All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 16,459
- 686
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse code review & quality skills
Showing 8,617–8,640 of 16,459 skills
- Sr SavePhase 9 of the SRS workflow. Saves all project context to _context/ files so future Claude sessions can resume without re-reading the full SRS.Votes: 0GitHub stars: 19
- Sr SavePhase 9 of the SRS workflow. Saves all project context to _context/ files so future sessions can resume without re-reading the full SRS.Votes: 0GitHub stars: 19
- Ck QualityIndependent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.Votes: 0GitHub stars: 19
- Ck PlanPlan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.Votes: 0GitHub stars: 19
- Ck Plan JsonCreate a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.Votes: 0GitHub stars: 19
- Ck FixFix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).Votes: 0GitHub stars: 19
- Sr SavePhase 9 of the SRS workflow. Saves all project context to _context/ files so future sessions can resume without re-reading the full SRS.Votes: 0GitHub stars: 19
- Strategic CompactSuggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.Votes: 0GitHub stars: 19
- Sr SavePhase 9 of the SRS workflow. Saves all project context to _context/ files so future Claude sessions can resume without re-reading the full SRS.Votes: 0GitHub stars: 19
- Simplification CascadesFind one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"Votes: 0GitHub stars: 19
- Scale GameTest at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scalesVotes: 0GitHub stars: 19
- Inversion ExerciseFlip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"Votes: 0GitHub stars: 19
- Problem SolvingCreative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplificationVotes: 0GitHub stars: 19
- Code ReviewAlways use this skill before claiming any work is done, fixed, passing, or complete — even if it seems obvious. Also use when receiving code review feedback from any source (human or automated), when finishing a task or major feature, before committing or creating a PR, or when about to express satisfaction with work. Covers three practices: receiving feedback with technical rigor (no performative agreement), triggering code review via /code-review command or cook/fix pipelines, and verificat...Votes: 0GitHub stars: 19
- Ck QualityIndependent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.Votes: 0GitHub stars: 19
- Ck PlanPlan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.Votes: 0GitHub stars: 19
- Ck Plan JsonCreate a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.Votes: 0GitHub stars: 19
- Ck FixFix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).Votes: 0GitHub stars: 19
- Codebase AnalysisPerforms deep static analysis of a codebase to generate a comprehensive, hierarchical, cross-referenced documentation ecosystem. Use this skill whenever the user wants to analyze, document, understand, or audit a codebase — even if they phrase it as "document my project", "analyze the repo", "generate docs", "audit technical debt", "understand this codebase", or "create documentation for this code". This skill covers: program structure extraction, architectural documentation, behavioral anal...Votes: 0GitHub stars: 2
- GovtechMaxim L3 pack. Bundles: FedRAMP + NIST 800-53 + Section 508. Primary framework: NIST 800-53 (federal security controls).Votes: 0GitHub stars: 2
- FintechMaxim L3 pack. Bundles: PCI-DSS + FINTRAC + SOX + FDX. Primary framework: PCI-DSS v4.0 (Payment Card Industry).Votes: 0GitHub stars: 2
- Agency All InMaxim L2 pack. Bundles: All six L1 packs. Primary framework: Behavioral Moat Framing Doctrine (ADR-007).Votes: 0GitHub stars: 2
- Professional OsMaxim L2 pack. Bundles: L1.1 + L1.2 + L1.3 + L1.4 + L1.5 (five L1 packs). Primary framework: COM-B (Michie et al.).Votes: 0GitHub stars: 2
- Founder OsMaxim L2 pack. Bundles: L1.1 AI Governance + L1.2 MemPalace Pro + L1.3 Proactive Watch. Primary framework: Fogg Behavior Model.Votes: 0GitHub stars: 2