Cut code review time & bugs in half Instantly.
Reviews for AI-powered teams who move fast (but don’t break things) ↗
home / skills / faulkdev / github-copilot-superpowers
faulkdev/github-copilot-superpowers
32 skills
GitHubSponsored
minimalist-surgical-development
faulkdev/github-copilot-superpowers
Use when editing an existing codebase and the goal is minimal, standard, and non-invasive changes - prioritizes simplest solution, standard libraries first, and surgical modification without unsolicited refactors
task-direction-approval
faulkdev/github-copilot-superpowers
Use when considering switching libraries/tools, changing architecture, or replacing automation with manual workarounds - explains root cause, offers 2-3 options with trade-offs, and requests explicit user choice
brainstorming
faulkdev/github-copilot-superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
receiving-code-review
faulkdev/github-copilot-superpowers
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
obra-subagent-driven-development
faulkdev/github-copilot-superpowers
Use when executing implementation plans with independent tasks in the current session
obra-finishing-a-development-branch
faulkdev/github-copilot-superpowers
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
obra-test-driven-development
faulkdev/github-copilot-superpowers
Use when implementing new behavior or fixing bugs via tests-first (TDD) in VS Code Copilot Agent mode.
obra-writing-plans
faulkdev/github-copilot-superpowers
Use when the user asks for a plan, roadmap, or step-by-step breakdown for a multi-step task in VS Code Copilot Agent mode.
obra-using-superpowers
faulkdev/github-copilot-superpowers
Use when working in VS Code Copilot Agent mode and you want the Superpowers workflow (plans, verification, debugging, TDD) applied consistently.
verification-before-completion
faulkdev/github-copilot-superpowers
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
obra-writing-skills
faulkdev/github-copilot-superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment
systematic-debugging
faulkdev/github-copilot-superpowers
Use when errors are unclear, flaky, or regressions occur; apply a disciplined debugging loop in VS Code Copilot Agent mode.
test-driven-development
faulkdev/github-copilot-superpowers
Use when implementing new behavior or fixing bugs via tests-first (TDD) in VS Code Copilot Agent mode.
using-superpowers
faulkdev/github-copilot-superpowers
Use when working in VS Code Copilot Agent mode and you want the Superpowers workflow (plans, verification, debugging, TDD) applied consistently.
writing-plans
faulkdev/github-copilot-superpowers
Use when the user asks for a plan, roadmap, or step-by-step breakdown for a multi-step task in VS Code Copilot Agent mode.
obra-systematic-debugging
faulkdev/github-copilot-superpowers
Use when errors are unclear, flaky, or regressions occur; apply a disciplined debugging loop in VS Code Copilot Agent mode.
dispatching-parallel-agents
faulkdev/github-copilot-superpowers
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
uncertainty-verification
faulkdev/github-copilot-superpowers
Use when providing exact commands, flags, config keys, file paths, API details, standards, or version-specific behavior - enforces verification via official docs (Context7/web fetch), explicit citations, and bans assumption-based specifics
executing-plans
faulkdev/github-copilot-superpowers
Use when you have a written implementation plan to execute in a separate session with review checkpoints
investigation-mode
faulkdev/github-copilot-superpowers
Use when there are 2+ consecutive failures, repeated errors, or the work feels stuck - pauses implementation, switches to root-cause investigation, gathers evidence, and resumes only after a verified plan and options
root-cause-tracing
faulkdev/github-copilot-superpowers
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
requesting-code-review
faulkdev/github-copilot-superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
obra-brainstorming
faulkdev/github-copilot-superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
obra-dispatching-parallel-agents
faulkdev/github-copilot-superpowers
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
obra-executing-plans
faulkdev/github-copilot-superpowers
Use when you have a written implementation plan to execute in a separate session with review checkpoints
obra-receiving-code-review
faulkdev/github-copilot-superpowers
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
obra-requesting-code-review
faulkdev/github-copilot-superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
faulkdev/github-copilot-superpowers
Use when executing implementation plans with independent tasks in the current session
obra-using-git-worktrees
faulkdev/github-copilot-superpowers
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
using-git-worktrees
faulkdev/github-copilot-superpowers
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
finishing-a-development-branch
faulkdev/github-copilot-superpowers
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
writing-skills
faulkdev/github-copilot-superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment