AI Agent & Automation Workflows

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.

YAML frontmatter standard for Awl agents and commands — required fields (name for agents, description for both), recommended fields (tools, model), optional metadata (version, category, color), the four-tier model assignment rules (inherit/haiku/sonnet/opus), and the validation rules enforced by /awl-meta:validate-frontmatter. Use this skill whenever Claude is editing or creating a file under plugins//agents/.md or plugins//commands/.md, writing YAML frontmatter for an Awl agent/command, running /awl-meta:validate-frontmatter or /awl-meta:create-workflow, or reviewing frontmatter in a PR diff. Make sure to use this skill whenever an Awl agent or command markdown file shows up in the context — writing incorrect frontmatter silently breaks plugin discovery.

Linear ticket state machine and workflow document conventions for Awl. Defines the Backlog → Research → Plan → In Dev → In Review → Done lifecycle, the "status update FIRST" rollback discipline, and the Research/Plan/Validation/Handoff/PR document naming patterns used to attach workflow artifacts to tickets. Use this skill whenever Claude sees a Linear ticket reference (PROJ-123, ENG-45, etc.), is about to call any mcplinear tool, transitions ticket status, creates or queries a workflow document attached to a ticket, or starts/finishes work that maps to a ticket. Make sure to apply this skill even when the user didn't invoke an Awl command — any mention of a Linear ticket is enough to trigger it.

Pull request lifecycle for Awl — branch naming, the commit → create-pr → describe → babysit → merge flow, Linear status transitions at each phase, PR description conventions, and the safety rules around rebasing, CI, and squash-merging. Use this skill whenever Claude is working on a feature branch (anything matching [A-Z]+-[0-9]+-), running git commands that will produce a PR, creating/describing/reviewing/merging a pull request, or when a GitHub PR URL shows up in the conversation. Make sure to use this skill whenever the user is about to run /awl-dev:commit, /awl-dev:create-pr, /awl-dev:describe-pr, /awl-dev:babysit-pr, or /awl-dev:merge-pr, even if they don't explicitly ask for PR guidance.