Browse Skills

A systematic debugging approach: add temporary JSONL logging to the real code path, reproduce the bug, and analyze runtime events to find the exact point of divergence before fixing. Use when static analysis gives low confidence or the bug involves runtime state, ordering, concurrency, or manual reproduction.

Runs pre-commit verification gates (types, format, typecheck, tests, i18n) in order, automatically fixes linting and formatting errors, and commits only when all checks pass. Use after completing a task or making changes to ensure code quality before committing.

Captures screenshot and element snapshot on browser errors during e2e testing, saving to gitignored .ai/scratch/e2e/. Invoke when 'Something went wrong', auth errors, blank pages, or unexpected redirects appear. A building block that captures and returns, leaving further action to the caller.

Orchestrates the bug-fix lifecycle from root cause analysis to implementing and proving the fix with a mandatory red→green regression test. Use when fixing a bug, test failure, or unexpected behavior.

Interviews the user relentlessly, one question at a time, to resolve every open decision in a plan, spec, or design idea. Cross-checks answers against the codebase and domain glossary, records resolutions immediately, and surfaces contradictions. Supervised use only.

Audits the Carbon codebase as a senior advisor to surface improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX) and produces self-contained implementation plans for other AI agents to execute. Strictly read-only; never modifies code.

Generates a self-contained HTML page that explains a pull request's purpose, changes, and verification, helping reviewers quickly understand complex changes without reading the full diff.

Break a large pull request into smaller, reviewable PRs (stacked or parallel) while preserving all original work. Use when a PR is too big, mixes refactors with features, or requires incremental delivery.

Performs read-only root cause analysis for bugs, test failures, and unexpected behaviors. Produces a brief identifying the root cause, files to change, approach, and risks, without making any edits or state changes.

Provides guidelines for writing idiomatic Rust code, covering borrowing, error handling, performance, testing, and documentation. Use when writing, reviewing, or refactoring Rust code.

Critically reviews your own branch diff against main before opening or merging a PR, identifying must-fix issues, risks, improvements, and docs-freshness checks. Supports an opt-in strict thermo-nuclear mode for deep maintainability audits.

Quick end-to-end smoke test of the local Carbon ERP dev server: logs in and verifies core modules (dashboard, sales, purchasing, etc.) render without errors. Use after booting, broad changes, or when asked to smoke test.