Menú
Use this skill when asked to create or amend a commit.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Write plans intended for a cheaper or less capable implementation model. Use when the user asks for a plan suitable for another LLM, junior engineer, intern, cheaper model, coding agent, or implementation delegate.
Use when the user asks for ideas, brainstorming, discussion, exploration, possibilities, pros and cons, tradeoffs, or to "think through" something.
Use this skill when asked to plan something, or plan and implement. Do not use when asked to implement a plan.
Use when initializing Rust projects or modifying Cargo.toml, Cargo.lock, cargo config, or other cargo-related files. Prefer this skill for dependency changes, features, package metadata, workspaces, and cargo commands. Do not load it for editing Rust source code generally.
Split an existing commit or PR into smaller reviewable pieces through a one-hunk patch queue. Use when extracting part of a commit, splitting a commit into multiple commits, or splitting PR changes from one or more source commits without starting from direct source edits.
Checkpoint, inspect, and return through session tree branches. Use when exploring uncertain approaches, investigating code, or when the user asks for a forked agent.
| name | commit |
| description | Use this skill when asked to create or amend a commit. |
Use this skill whenever creating or amending a commit.
Run:
scripts/fetch-commit-guidelines.sh
Use that output as the source of truth for commit format/rules.
Exception: Do not manually wrap lines or enforce maximum line length, ignore any instructions to the contrary.
Commit messages are reused as PR descriptions, so optimize for skimmability:
Run:
scripts/commit-footer-from-issue.sh <github-issue-number>
Or specify repo explicitly:
scripts/commit-footer-from-issue.sh <github-issue-number> owner/repo
Append the output at the end of the commit message.
The script always prints Closes #<issue>. If a Linear linkback comment exists on the GitHub issue, it also prints Closes [ABC-123](https://linear.app/...).