fbac
UserNot every change should be shipped. Not every passing review means a change is ready. Make your AI agents earn the word "done".
Categories
Indexed Skills (16)
brainstorming
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior, before any implementation action. Umbrella flavor: use this instead of umbrella:brainstorming.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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
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
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
review-lens
Use when reviewing a diff, branch, or PR, before declaring work done, requesting code review, or merging — especially changes touching shared surfaces (headers, nav, shells) or auth/route gating, or before finishing a development branch.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
using-umbrella
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
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
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code. Umbrella flavor — use this instead of umbrella:writing-plans.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
minimal-testing
Use when implementing any feature or bugfix, once the change works, to decide which tests to write - the absolute minimum set that proves the change, preferring real calls over mocks
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.