Awl Conventional Commits
Conventional commit format rules for Awl — commit types (feat/fix/perf/revert for changelog; docs/style/refactor/test/build/ci/chore for internal), scope detection from changed-file paths, header format (max 100 chars, imperative mood, no trailing period), body and footer conventions, Linear ticket footer extraction from branch names, and the Awl-specific rule against adding Co-authored-by: Claude attribution to plain commits. Use this skill whenever Claude is about to run git commit, being asked to write or fix a commit message, invoking /awl-dev:commit, or reviewing commit messages in a PR. Make sure to use this skill whenever a commit is about to be created, even if the user didn't explicitly ask for format guidance — writing commits in the wrong format breaks changelog generation.
Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format
Category: Other — see all ranked ›
Install (Claude Code):
cp -r awl-conventional-commits ~/.claude/skills/- Adoption: 1 repos
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
source ↗ · skill:Threading-Needles/awl-conventional-commits
Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›
Measured 2026-08-03 · scorer s5 · how · something wrong here?