Loading...
Loading...
Found 41 Skills
Keep README files current with project changes. Use when project structure changes, features added, or setup instructions modified. Suggests README updates based on code changes. Triggers on significant project changes, new features, dependency changes.
Fix build and TypeScript errors with minimal changes
Create Antigravity-style implementation plans with strict review gates, line-item IDs, and no code changes until the user explicitly says Execute Plan.
Use when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates
Generate a map of all files relevant to a task before making changes
Summarize code changes by author type and scope. Inputs are author and scope with product plus PR as defaults.
Review all unresolved PR review threads, address them by making necessary code changes, and commit the changes appropriately.
Tracked lightweight execution with composable rigor flags for tasks between a typo fix and a full feature. Plan + execute with optional --discuss, --research, and --full flags to add rigor incrementally. Use for "quick task", "small change", "ad hoc task", "add a flag", "extract function", "small refactor", "fix bug in X". Do NOT use for multi-component features, architectural changes, or anything needing wave-based parallel execution — those are Simple+ tier.
Update documentation after code changes. Use when adding features, changing keybindings, modifying config options, or updating TUI behavior. Automatically finds and updates relevant documentation files (README, recipes, help text).
Validate code changes by intelligently selecting and running the appropriate test suites. Use this when editing code to verify changes work correctly, run tests, validate functionality, or check for regressions. Automatically discovers affected test suites, selects the minimal set of venvs needed for validation, and handles test execution with Docker services as needed.
Create a PR title and draft description after substantive code changes are finished. Trigger when wrapping up a moderate-or-larger change (runtime code, tests, build config, docs with behavior impact) and you need the PR-ready summary block with change summary plus PR draft text.
Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally. Use when you need to understand what user interactions and API calls a test covers, or when you want network mocks for writing tests.