GitHub
pr-review
Review GitHub PRs with inline comments and structured summaries. Use when reviewing PRs via gh CLI.
☆ 0View skill
srnnkls AI Skills
GitHub ↗Browse published AI skills maintained by srnnkls. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
24Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
spec-promote
Promote spec from draft to active stage. Use after spec review passes or when ready to begin implementation.
☆ 0View skill
GitHub
code-review-receive
Technical evaluation of code review feedback. Use when receiving review feedback - requires verification before implementing, no performative agreement, push back when technically wrong.
☆ 0View skill
GitHub
spec-create
Create spec documents (spec.md, context.md, tasks.yaml, dependencies.yaml, validation.yaml). Receives validation data from spec-validate.
☆ 0View skill
GitHub
spec-issues-create
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.
☆ 0View skill
GitHub
spec-review
Multi-agent spec review with parallel Claude/OpenCode reviewers. Use after spec-create or standalone via /spec.review.
☆ 0View skill
GitHub
spec-update
Update spec documents by analyzing git history to sync task status with reality.
☆ 0View skill
GitHub
task-dispatch
Subagent-driven task execution with TDD workflow. Dispatches tester subagent (writes failing tests) then implementer subagent (makes tests pass), with batch review.
☆ 0View skill
GitHub
dotfiles-manage
Manage dotfiles using dotter (symlink manager and templater). Use when deploying, adding, removing, or organizing configuration files in ~/dotfiles.
☆ 0View skill
GitHub
spec-clarify
Resolve ambiguities and markers in validation.yaml interactively. Updates spec docs directly with full audit trail.
☆ 0View skill
GitHub
code-test
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.
☆ 0View skill
GitHub
spec-archive
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...
☆ 0View skill
GitHub
git-worktree-use
Create isolated git worktrees with safety verification. Use when starting feature work needing isolation or before executing plans - systematic directory selection and baseline verification.
☆ 0View skill
GitHub
bash-use
Ultra-concise bash command patterns. Use when constructing shell commands or one-liners.
☆ 0View skill
GitHub
hooks-test
Test Claude Code hooks in isolation and via integration. Use when developing, debugging, or validating hook behavior.
☆ 0View skill
GitHub
skill-create
Create new Claude Code skills following project patterns and best practices. Use when building new skills, extracting reusable capabilities, or converting commands to skills.
☆ 0View skill
GitHub
code-debug
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.
☆ 0View skill
GitHub
debate-start
Start structured red vs. blue team debates via subagents. Use when exploring a topic from multiple adversarial perspectives.
☆ 0View skill
GitHub
task-completion-verify
Evidence-based completion claims. Use before claiming work is complete, fixed, or passing - requires running verification commands and confirming output before any success claims.
☆ 0View skill
GitHub
docs-implement
General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.
☆ 0View skill
GitHub
spec-validate
Validation loop for speccing. Clarifies requirements through structured questioning before document creation.
☆ 0View skill
GitHub
code-review
Code review methodology. Use when reviewing code locally or preparing for a PR review.
☆ 0View skill
GitHub
clarify
Resolve ambiguities interactively with tracked changes. Works with spec-create, spec-review, code-review, and other skills.
☆ 0View skill
GitHub
task-continue
Resume spec implementation from checkpoint. Use when continuing task-dispatch after context limit or session break.
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.