Menu
Ard commit and PR title format. Use before creating commits, rewriting commit messages, or opening/updating PRs.
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
Investigate and fix a GitHub issue using Ard's preferred TDD workflow. Use when asked to work on, investigate, fix, or create a branch/PR for a GitHub issue or bug report.
Cut a new Ard version release end-to-end. Creates and pushes a new version tag, waits for the Release Binaries workflow to build and publish the GitHub release, then drafts and updates release notes. Use when a batch of changes is ready to ship as a new version.
Generate release notes for a new Ard version tag. Compares the diff between two tags, summarizes user-facing changes (features, fixes, breaking changes), and publishes via `gh release edit`. Use when a new version tag has been pushed and needs release notes.
Tree-sitter grammar and highlighting maintenance for Ard (tree-sitter/grammar.js and tree-sitter/queries/*.scm), including syncing highlights to Zed. Use when updating the grammar, fixing tree-sitter highlight errors, or revising Ard syntax highlighting queries.
| name | commit-format |
| description | Ard commit and PR title format. Use before creating commits, rewriting commit messages, or opening/updating PRs. |
Ard enforces Conventional Commit headers for commit messages and PR titles.
<type>(<scope>)!: <description>
The scope and breaking-change marker are optional, so these are valid:
feat(lsp): add member completions
fix(checker): continue after invalid call arity
docs: document release flow
refactor(parser)!: simplify function parsing
buildchorecidocsfeatfixperfrefactorrevertstyletestWhen a commit fully fixes a tracked GitHub issue, include a closing reference in the commit body, e.g.:
Fixes #218
Use a non-closing reference such as Refs #218 when the commit is related but does not fully resolve the issue.
Before pushing commits or creating/updating a PR title, validate the header with:
scripts/validate-commit-message.sh --message "feat(lsp): add member completions"
For commit message files, use:
scripts/validate-commit-message.sh .git/COMMIT_EDITMSG
PR titles are checked with the same format. Use a Conventional Commit title such as:
feat(lsp): add navigation and editing features