Browse Skills

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.

Runs validation gates (type generation, linting, typecheck, tests, i18n) on changed files, auto-fixes issues, and commits only when everything passes. Use after code changes to ensure a safe commit.

Surveys how best-in-class ERPs and point solutions implement a feature, producing a structured findings file. Use when designing a new feature, evaluating approaches, or answering industry-standard questions.

Automates the iterative development of a single, tightly-scoped work item (bug, tweak, small feature) by running a doer→gate→judge cycle unattended, producing a gated pull request as the only human supervision point.

Creates or refreshes an AGENTS.md for Carbon packages or ERP modules by reading source code, grounding every claim in real functions, tables, and exports. Ideal when adding modules or performing freshness audits.

Generates or refreshes an AGENTS.md for a Carbon package or ERP module by reading actual source code, verifying every claim against real functions, tables, and exports. Use when adding a new module, when audits flag a stale file, or on request.

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.

Captures screenshot and element snapshot of current browser page when an error appears during e2e testing. Saves to gitignored .ai/scratch/e2e/. Use when agent-browser snapshot shows failure indicators. Building block: captures and returns, caller decides to continue.

Executes an approved implementation plan task by task, running verifications and committing each task via a check-and-commit gate. Use after /plan approval for automated, verifiable implementation of software plans.

Executes an approved implementation plan step by step, running verifications and committing per task. Use after a plan is approved to turn it into working, tested code.

Orchestrates the complete feature lifecycle from research and spec writing to plan, build, test, and self-review. Supports autonomous and approval-based modes with structured run records.

An end-to-end bug-fix pipeline that diagnoses root causes, implements minimal fixes with regression tests, and optionally verifies and commits. Use for fixing bugs, test failures, or unexpected behavior.