Topic: skills
17,247 skills in this topic.
-
dockerfile-generator
abdullah1854/ClaudeSuperSkills 1
-
memory-systems
abdullah1854/ClaudeSuperSkills 1
-
pr-summary
abdullah1854/ClaudeSuperSkills 1
-
tool-design
abdullah1854/ClaudeSuperSkills 1
-
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
-
create-plan
Create comprehensive implementation plan in .plans directory based on analysis or report. Use when user asks to create a plan, plan implementation, design a solution, or structure work for a feature/refactor/fix.
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
-
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
-
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
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
-
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Cygnusfear/claude-stuff 3
-
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Cygnusfear/claude-stuff 3
-
axiom-audit
ONLY USE WHEN REPO IS USING AXIOM LOGGING. Audit Axiom logs to identify and prioritize errors and warnings, research probable causes, and flag log smells. Use when user asks to check Axiom logs, analyze production errors, investigate log issues, or audit logging patterns.
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
-
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
-
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
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
-
file-name-wizard
Audit all filename and naming conventions in the codebase against CLAUDE.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.
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
-
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Cygnusfear/claude-stuff 3
-
design-spec-extraction
Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.
Cygnusfear/claude-stuff 3
-
using-superpowers
Guidelines for using skills effectively - load relevant skills before complex tasks, not every message
Cygnusfear/claude-stuff 3
-
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
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