pr-review
Review GitHub PRs with inline comments and structured summaries. Use when reviewing PRs via gh CLI.
Explorez les skills IA publiés de srnnkls et consultez leurs instructions source.
Skills indexés
24Étoiles des dépôts des skills indexés
0Forks du dépôt
0Moyenne des étoiles par skill indexé
0Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Review GitHub PRs with inline comments and structured summaries. Use when reviewing PRs via gh CLI.
Promote spec from draft to active stage. Use after spec review passes or when ready to begin implementation.
Technical evaluation of code review feedback. Use when receiving review feedback - requires verification before implementing, no performative agreement, push back when technically wrong.
Create spec documents (spec.md, context.md, tasks.yaml, dependencies.yaml, validation.yaml). Receives validation data from spec-validate.
Generate GitHub issue drafts from spec directories, creating initiative/feature/task markdown files with gh CLI commands. Use when converting specs to GitHub issues or setting up issue tracking for features.
Multi-agent spec review with parallel Claude/OpenCode reviewers. Use after spec-create or standalone via /spec.review.
Update spec documents by analyzing git history to sync task status with reality.
Subagent-driven task execution with TDD workflow. Dispatches tester subagent (writes failing tests) then implementer subagent (makes tests pass), with batch review.
Manage dotfiles using dotter (symlink manager and templater). Use when deploying, adding, removing, or organizing configuration files in ~/dotfiles.
Resolve ambiguities and markers in validation.yaml interactively. Updates spec docs directly with full audit trail.
Enforce test-driven development (RED-GREEN-REFACTOR). Use when implementing features, fixing bugs, or changing behavior - write failing test first, then minimal code to pass.
Archive completed development specs from ./specs/active/ to ./specs/archive/, updating documents with completion status and maintaining archive index. Use when finishing tasks or moving completed work to archiv...
Create isolated git worktrees with safety verification. Use when starting feature work needing isolation or before executing plans - systematic directory selection and baseline verification.
Ultra-concise bash command patterns. Use when constructing shell commands or one-liners.
Test Claude Code hooks in isolation and via integration. Use when developing, debugging, or validating hook behavior.
Create new Claude Code skills following project patterns and best practices. Use when building new skills, extracting reusable capabilities, or converting commands to skills.
Systematic debugging with root cause tracing. Use when encountering bugs, test failures, or unexpected behavior - find root cause before attempting fixes, trace backward through call chain.
Start structured red vs. blue team debates via subagents. Use when exploring a topic from multiple adversarial perspectives.
Evidence-based completion claims. Use before claiming work is complete, fixed, or passing - requires running verification commands and confirming output before any success claims.
General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.
Validation loop for speccing. Clarifies requirements through structured questioning before document creation.
Code review methodology. Use when reviewing code locally or preparing for a PR review.
Resolve ambiguities interactively with tracked changes. Works with spec-create, spec-review, code-review, and other skills.
Resume spec implementation from checkpoint. Use when continuing task-dispatch after context limit or session break.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.