Code Review
Automated code review and analysis
autonomous-orchestration
by troykelly
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers, monitors progress, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
features-documentation
by troykelly
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
apply-all-findings
by troykelly
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
code-architect
by troykelly
Use when asked for an architecture blueprint or explicitly asked to run the code-architect subagent.
debug
by thechandanbhagat
Debug code, analyze errors, interpret stack traces, find root causes, and suggest fixes. Use when troubleshooting bugs, analyzing crashes, or investigating unexpected behavior.
nanny
by Michaelliv
Break a goal into tasks, execute them one by one, retry on failure. Use when the user asks to build a feature, implement something multi-step, or says "nanny this" or "orchestrate this." Not for single quick edits — for work that has multiple steps and needs to be tracked.
project-status-sync
by troykelly
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
Verified Review Skill
by cdeistopened
```
code-review
by thechandanbhagat
Perform automated code reviews with best practices, security checks, and refactoring suggestions. Use when reviewing code, checking for vulnerabilities, or analyzing code quality.
ci-monitoring
by troykelly
Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable
review-gate
by troykelly
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met
by thechandanbhagat
Work with PDF files - read, extract text/images/tables, create PDFs, merge, split, and convert PDFs. Use when the user asks to read, create, modify, or analyze PDF documents.
deferred-finding
by troykelly
Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process
issue-lifecycle
by troykelly
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
issue-driven-development
by troykelly
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
spec-reviewer
by EnzeD
Review and challenge spec documents against the project's codebase, best practices, and guidelines. Spawns a team of parallel agents to analyze consistency, code reuse, performance, scope, and testability. Use when the user says "challenge", "review spec", "check spec", "audit spec", or asks to validate a spec file against the codebase. Triggers on spec file paths (e.g., specs/037-hover-brackets-info.md).
session-start
by troykelly
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
review-scope
by troykelly
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
pr-test-analyzer
by troykelly
Use when asked to evaluate PR test coverage or explicitly asked to run the pr-test-analyzer subagent.
api-documentation
by troykelly
Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.
branch-discipline
by troykelly
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
conflict-resolution
by troykelly
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
security-review
by troykelly
MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential code
inclusive-language
by troykelly
Use when writing code, documentation, or comments - always use accessible and respectful terminology