Menu
Generate conventional commit messages for this repository. Use when the user asks to commit changes, create a commit, or generate a commit message.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Uses the aether-session-index CLI to inspect local Aether session logs for self-improvement, debugging, tool-use patterns, failures, and optimization opportunities. Use when asked to analyze agent behavior, improve Aether usage, find recurring tool errors, review context usage, or optimize workflows from session history.
Rust best practices, idiomatic patterns, and project conventions. Use when writing Rust code, reviewing PRs, debugging issues, or working with error handling, traits, concurrency, or cargo tooling.
Authoritative documentation for Aether itself — its settings, built-in MCP servers, agents, terminal UI, and how to run it. Use whenever the user asks how Aether works, how to configure it, or about its features, commands, or settings.
Reviews the current branch, including staged and unstaged changes, and outputs prioritized recommendations to simplify architecture and reduce complexity. Use when the user wants a staff-level review of the current branch without modifying files.
Best practices for writing AI agent skills with a SKILL.md file. Use anytime you're asked to write, review or update a skill.
| name | commit-message |
| description | Generate conventional commit messages for this repository. Use when the user asks to commit changes, create a commit, or generate a commit message. |
| allowed-tools | ["Bash(git status:*)","Bash(git diff:*)","Bash(git log:*)","Bash(git add:*)","Bash(git commit:*)","Read","AskUserQuestion"] |
Generate commit messages following this repository's conventional commit standards.
feat, fix, chore, refactor, docs, test(gateway), (frontend), (deps), (deps-dev), (infra)<type>(<scope>): <subject> or <type>: <subject>CON-XXX in subject when relevantfeat: add user authentication endpoint
fix(gateway): handle connection timeout gracefully
chore(deps): bump sentry-rust from 0.31 to 0.32
refactor: extract validation logic into separate module
feat(frontend): expose client connection details on dashboard (CON-244)
# Check staging area
git status
# View staged changes (if any)
git diff --cached
# View unstaged changes
git diff
# Recent commits for style reference
git log --oneline -5
Based on the changes:
| Change Type | Prefix |
|---|---|
| New feature or capability | feat |
| Bug fix | fix |
| Dependencies, configs, build | chore |
| Code restructuring (no behavior change) | refactor |
| Documentation only | docs |
| Tests only | test |
Infer from changed file paths:
| Path Pattern | Scope |
|---|---|
gateway/ | (gateway) |
frontend/ | (frontend) |
infra/, terraform/ | (infra) |
Cargo.toml, package.json (deps only) | (deps) |
| Dev dependencies | (deps-dev) |
Omit scope if changes span multiple areas or scope isn't clear.
Add a body when:
Body format:
Stage and commit the changes:
git add -A && git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body if needed>
EOF
)"