--- name: awl-conventional-commits description: 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. --- # Awl Conventional Commits Every commit in an Awl-managed repo follows the conventional-commits format. This skill defines the exact shape, the type taxonomy, the scope detection rules, and the Awl-specific attribution policy. The full spec (with all examples) lives in `references/conventional-commits.md`. ## The format ``` ():