33 skills published by serpro69 across 1 repository. Together they weigh 135 941 tokens — that is what loading all of them at once would cost you in context.
33 skills 135 941 tokens total
| Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
| Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
|
|
| Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.
| Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.
| Compare two versions of a skill's instructions to detect degradations and complexity increases. Asymmetric check — only regressions count. Additions, clarifications, and strengthenings are not degradations. Compares HEAD → working tree by default. Walks the full reachable file set from SKILL.md via markdown links. Produces a report file under docs/reviews/diff-skill/ and an inline summary.
| Compare two versions of a skill's instructions to detect degradations and complexity increases. Asymmetric check — only regressions count. Additions, clarifications, and strengthenings are not degradations. Compares HEAD → working tree by default. Walks the full reachable file set from SKILL.md via markdown links. Produces a report file under docs/reviews/diff-skill/ and an inline summary.
| After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.
| After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.
An example skill for testing diff-skill evaluation.
An example skill for testing diff-skill evaluation.
An example skill for testing diff-skill evaluation.
An example skill for testing diff-skill evaluation.
A Go security skill for reviewing code
Go testing best practices
| docs/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Provides structured execution with profile detection, dependency handling, review checkpoints.
| docs/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Provides structured execution with profile detection, dependency handling, review checkpoints.
| Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
| Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
| Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
| Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
| Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
| Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
| Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
| Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
Reviews tool configurations for correctness.
Reviews tool configurations for correctness.
Reviews tool configurations for correctness.
Reviews tool configurations for correctness.
A test skill