skills

Create and update AGENTS.md project rules. Use when authoring or amending the cross-tool conventions agents must follow.

Write forward-looking startup instructions for the next session, then reset context to save costs. Use when the context is getting long or before switching focus.

Run pre-release checks, pick the version bump, and cut the release. Use when ready to tag and release.

Create and maintain a specification that states what to build, not how. Use when writing a spec, editing requirements, or defining acceptance criteria.

Run all review dimensions against a diff or a path. Use when reviewing a feature branch before merge, reviewing someone else's PR, or auditing a file path.

Create or update project documentation. Use when creating architecture docs, runtime docs, reference docs, or design documents that explain what the system does.

Review architecture, boundaries, and design consistency. Use when reviewing module boundaries, extension seams, or contract drift.

Implement features incrementally through vertical slices. Use when building features, adding functionality, or implementing tasks that touch multiple files.

Review whether changed logic does what it claims — bugs, edge cases, broken contracts. Use when reviewing a diff for correctness, not just style or structure.

Debug systematically with structured triage. Use when tests fail, builds break, or runtime behavior doesn't match expectations.

Deprecate and remove code safely. Use when replacing systems, removing unused features, or consolidating duplicate implementations.

Design stable interfaces that are hard to misuse. Use when defining contracts, module boundaries, or public APIs.

Review docs for drift, missing updates, and terminology changes. Use when code changes should be reflected in documentation.

Manage commits, branches, and change history. Use when committing, branching, or managing version control.

Create a GitHub issue from a short description. Use when filing a bug, feature request, or task.

Design a feature or behavior change through dialogue. Use when asked to plan, scope, design, or break down work before coding.

Create a pull request with review and verify. Use when the branch is ready to merge.

Review security risks, trust boundaries, and unsafe defaults — concrete attack paths only. Use when reviewing security posture or assessing risk before release.

Simplify code by reducing complexity while preserving exact behavior. Use after a feature is working, during review when complexity is flagged, or when encountering unclear code.

Review code style, naming, patterns, and consistency. Use when reviewing code quality or style drift.

Drive implementation with red-green-refactor. Use when building features or fixing bugs test-first.

Review test adequacy for changed code — meaningful gaps, quality problems, and unnecessary tests. Use when reviewing whether changed code has adequate tests.