Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Cygnusfear/claude-stuff 3
-
create-mcp-skill
Create a new skill that uses an MCP server, following best practices from the MCP CLI guide. Use when user wants to create a skill for a new MCP server or integrate MCP functionality into a skill.
Cygnusfear/claude-stuff 3
-
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Cygnusfear/claude-stuff 3
-
systematic-debugging
ONLY USE THIS SKILL UPON USER/HOOMAN REQUEST TO USE EXACTLY THIS SKILL, ONLY RUN ON HOOMAN [OK]. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Cygnusfear/claude-stuff 3
-
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
Cygnusfear/claude-stuff 3
-
4-step-program
Coordinator workflow for orchestrating dockeragents through fix-review-iterate-present loop. Use when delegating any task that produces code changes. Ensures agents achieve 10/10 quality before presenting to human.
Cygnusfear/claude-stuff 3
-
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Cygnusfear/claude-stuff 3
-
comprehensive-code-review
This skill should be used when reviewing pull requests, performing comprehensive code review, analyzing code changes before merge, or when the user asks for thorough/ultra-critical code review. Performs EXTREMELY CRITICAL 6-pass analysis identifying runtime failures, code consistency issues, architectural problems, environment compatibility risks, and verification strategies. Posts structured review as GitHub PR comment. Use when user asks to "review PR", "review this code", "review changes", "check this PR", "analyze PR", "post review", or for Phase 3 of devflow. Supports parallel review mode with multiplier (code-review-3, code-review 6X) for consensus-based reviews. This is an ultra-critical reviewer that does not let things slip and desires only perfection.
Cygnusfear/claude-stuff 3
-
superpower-zustand
MANDATORY for creating Zustand stores. This skill is required when users request state management, creating stores, or mention Zustand. Do NOT create Zustand stores without this skill - all stores must use the required StoreBuilder pattern with immer middleware and factory pattern separation
Cygnusfear/claude-stuff 3
-
review-changes
Code review of current git changes, compare to related plan if exists, identify bad engineering, over-engineering, or suboptimal solutions. Use when user asks to review changes, check git diff, validate implementation quality, or assess code changes.
Cygnusfear/claude-stuff 3
-
create-skill
This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Cygnusfear/claude-stuff 3
-
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Cygnusfear/claude-stuff 3
-
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Cygnusfear/claude-stuff 3
-
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Cygnusfear/claude-stuff 3
-
writing-clearly-and-concisely
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
Cygnusfear/claude-stuff 3
-
update-docs
Update all documentation in .plans, CLAUDE.md files, docs, and .tasks to match current codebase state. Use when user asks to update docs, refresh documentation, sync docs with code, or validate documentation accuracy.
Cygnusfear/claude-stuff 3
-
audit
Run comprehensive codebase audit for gaps, deprecated code, TODOs, FIXMEs, architectural anti-patterns, type issues, and code smells. Use when user asks to audit code, find issues, check code quality, or identify architectural problems.
Cygnusfear/claude-stuff 3
-
blitz
This skill should be used when parallelizing multi-issue sprints using git worktrees and parallel Claude agents. Use when tackling multiple GitHub issues simultaneously, when the user mentions "blitz", "parallel sprint", "worktree workflow", or when handling 3+ independent issues that could be worked on concurrently. Orchestrates the full workflow from issue triage through parallel agent delegation to sequential merge.
Cygnusfear/claude-stuff 3
-
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Cygnusfear/claude-stuff 3
-
obsidian-upgrade
Upgrade Obsidian wikis to latest format. Handles structure migration (phases/tasks → features/specs), comment format upgrades (adding emoji prefixes), and Johnny Decimal feature organization. Use when user mentions "upgrade wiki", "migrate wiki", "update wiki format", or has old-format comments.
Cygnusfear/claude-stuff 3
-
create-subagent
This skill should be used when creating custom subagents for Claude Code, configuring specialized AI assistants, or when the user asks about agent creation, agent configuration, or delegating tasks to subagents. Covers both file-based agents and Task tool invocation.
Cygnusfear/claude-stuff 3
-
check-plan
Audit implementation progress against a plan, verify completed work, identify remaining tasks, and validate quality. Use when user asks to check plan status, verify implementation, see what's left to do, or validate plan completion.
Cygnusfear/claude-stuff 3
-
create-pr
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
Cygnusfear/claude-stuff 3
-
architectural-analysis
Deep architectural audit focused on finding dead code, duplicated functionality, architectural anti-patterns, type confusion, and code smells. Use when user asks for architectural analysis, find dead code, identify duplication, or assess codebase health.
Cygnusfear/claude-stuff 3