@cleepi/git 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,67 @@
+# Changelog — @cleepi/git
+
+All notable changes to this package are documented here.
+
+Format: [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/).
+Versioning: [SemVer](https://semver.org/spec/v2.0.0.html). Pre-`1.0.0`,
+minor bumps may include breaking changes.
+
+## [Unreleased]
+
+## [0.1.0] — 2026-05-28
+
+Initial release. Cleepi's git conventions as a pi package. Per
+[spec DRAFT-001](../../docs/DRAFT-001-cleepi-git-v0.1.0/spec.md)
+(accepted 2026-05-28).
+
+### Added
+
+- **`skills/git-commit/SKILL.md`** — canonical commit-message
+  convention. Conventional Commits + AngularJS type set
+  (`feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`,
+  `chore`, `build`, `ci`, `revert`). Hard rules: subject-line
+  only, NEVER `Co-authored-by:`, no `Signed-off-by:`, no emoji,
+  no trailing period, imperative + present tense + lowercase
+  first letter. Anti-pattern table with 8 worked examples.
+- **`prompts/commit.md`** — `/commit <type> <message>` slash
+  command. Resolves domain from cwd (nearest `packages/<n>/`
+  ancestor) and ticket-id from cwd → git branch → ask.
+  Strips any `Co-authored-by:` injected by AI tooling before
+  passing to `git commit`. Warns on unstaged changes; never
+  auto-`git add -A` without asking.
+- **`SPEC.md`** — package purpose-and-scope.
+- **`README.md`** — install, examples, soft-aware integration
+  with `@cleepi/sdd`.
+
+### Decisions captured in spec DRAFT-001
+
+- New `@cleepi/git` package rather than folding into
+  `@cleepi/coding` or `@cleepi/sdd` — keeps package taxonomy
+  clean, leaves room for branch / PR / rebase additions.
+- Subject-line only, no body, no footers — Honza-mandated.
+  Cleepi commit history reads as a list of one-liners.
+- Ticket-id highly recommended but not required — matches the
+  same gradient as `sdd`'s `DRAFT-NNN` vs real-ticket strictness.
+- Both skill and `/commit` prompt ship in v0.1.0 — skill carries
+  the convention; prompt is ergonomic glue.
+
+### Known limitations
+
+- `/commit` is designed for interactive pi sessions. In `--print`
+  non-interactive mode the AI tends to shortcut to bare
+  `<type>: <message>` format without resolving domain/ticket-id
+  from cwd. If you script commits, write the assembled message
+  yourself per the skill.
+
+### Not in this release (deferred)
+
+- `commit-msg` git hook (convention-led, not enforced).
+- Branch naming, PR templates, rebase discipline. v0.2.0+
+  candidates that justify keeping `@cleepi/git` separate.
+- Type extension via config. Teams wanting other types edit a
+  project-scope copy of the skill.
+- Multi-line bodies, `BREAKING CHANGE:` footer. Use `!` syntax
+  for breaks; put rationale in the spec, not the commit.
+
+[Unreleased]: https://github.com/cleevio/cleepi/compare/git-v0.1.0...HEAD
+[0.1.0]: https://github.com/cleevio/cleepi/releases/tag/git-v0.1.0

package/README.md

@@ -0,0 +1,120 @@
+# @cleepi/git
+
+Cleepi's git conventions as a pi package. Install in any repo
+where you want a clean, standardised commit history — and never
+another `Co-authored-by: Claude` line ever again.
+
+## What's in the box
+
+- **Skill** (`skills/git-commit/SKILL.md`) — the canonical
+  commit-message convention (Conventional Commits + AngularJS
+  types, with monorepo-aware domain and ticket-id discipline).
+  Loaded automatically when you ask about commits, or
+  explicitly with `/skill:git-commit`.
+- **Prompt** — `/commit <type> <message>`. Resolves domain
+  (from cwd) and ticket-id (from cwd → branch → ask), assembles
+  the message, strips any `Co-authored-by:` slop, asks before
+  committing.
+
+## The 30-second version
+
+Every cleepi commit follows this shape:
+
+```
+<type>(<domain>): [<ticket-id> ]<message>
+```
+
+Examples:
+
+```
+feat(crew): AC-201 add reviewer pre-step
+refactor(sdd): AC-202 collapse Why-now into Why
+docs(crew): fix README install path
+chore(meta): bump prettier
+fix(atlassian): DRAFT-007 handle empty JQL response
+```
+
+**Hard rules (non-negotiable):**
+
+- One line. No body. No footers.
+- **NEVER `Co-authored-by:`.** Not for AI assistants. Not for
+  anyone. Strip it if your tooling tries to add it.
+- No `Signed-off-by:` either.
+- No emoji, no trailing period.
+- Imperative, present tense, lowercase first letter of message.
+
+For the full discipline (type table, domain rules, ticket-id
+resolution chain, anti-patterns, voice), see
+[`skills/git-commit/SKILL.md`](skills/git-commit/SKILL.md). It's
+the source of truth.
+
+## Install
+
+Global (every pi session gets the convention):
+
+```bash
+pi install git:github.com/cleevio/cleepi/packages/git
+```
+
+Project-local (recommended for repos adopting the convention as
+their actual standard):
+
+```bash
+cd <repo>
+pi install -l git:github.com/cleevio/cleepi/packages/git
+```
+
+## How `/commit` works
+
+```
+/commit feat add reviewer pre-step
+```
+
+1. Validates `feat` against the Angular type set.
+2. Resolves domain: cwd is inside `packages/crew/` → `crew`.
+3. Resolves ticket-id: cwd is under
+   `docs/AC-201-reviewer-prestep/` → `AC-201`.
+4. Assembles: `feat(crew): AC-201 add reviewer pre-step`.
+5. Strips any `Co-authored-by:` injected anywhere.
+6. Shows you the message + the staged diff summary.
+7. Asks `[y / N / edit]` before running `git commit`.
+
+If you call `/commit` outside a `packages/<n>/` directory, or
+on a branch with no ticket pattern, it asks you for the
+missing pieces. Manual `--domain=...` and ticket-id tokens in
+the args always win.
+
+## Tuning
+
+Don't edit the package source — it gets overwritten on
+`pi update`. Instead, copy the skill into your project (or
+user) scope and edit there:
+
+```bash
+cp .pi/agent/git-commit/SKILL.md .pi/skills/git-commit/SKILL.md
+# edit .pi/skills/git-commit/SKILL.md
+```
+
+Project scope wins on collision.
+
+## Soft-aware integration with `@cleepi/sdd`
+
+`/commit` and `@cleepi/sdd`'s `/journal` share the same
+ticket-id resolution chain (cwd → branch → ask). When `sdd` is
+installed alongside `git`, ticket detection is consistent. When
+it isn't, branch-name and ask-user fallbacks still work.
+
+There is no hard dependency.
+
+## Related
+
+- [SPEC.md](./SPEC.md) — what this package is and isn't.
+- [CHANGELOG.md](./CHANGELOG.md) — release history.
+- Root cleepi [spec DRAFT-001](../../docs/DRAFT-001-cleepi-git-v0.1.0/spec.md) —
+  the v0.1.0 design rationale.
+- [`@cleepi/sdd`](../sdd/) — sibling package; shares ticket
+  resolution.
+- [Conventional Commits 1.0.0](https://www.conventionalcommits.org/)
+  — the upstream convention.
+- [AngularJS commit message guidelines](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#-commit-message-format)
+  — the upstream type set.

package/SPEC.md

@@ -0,0 +1,90 @@
+---
+title: "@cleepi/git"
+status: shipped
+created: 2026-05-28
+owner: Honza
+related:
+  - ../../docs/DRAFT-001-cleepi-git-v0.1.0/spec.md
+---
+
+# `@cleepi/git`
+
+## What this package is
+
+A pi package that ships Cleepi's git conventions as durable
+instructions. Install it in any repo and pi sessions there know
+how to write commits the cleepi way.
+
+Two things ship in v0.1.0:
+
+- **Skill** (`skills/git-commit/SKILL.md`) — the canonical
+  commit-message convention. Loaded on demand or with
+  `/skill:git-commit`.
+- **Prompt** — `/commit <type> <message>`. Resolves domain
+  (from cwd) and ticket-id (from cwd → branch → ask), assembles
+  the message, strips any AI-tooling-injected `Co-authored-by:`,
+  and runs `git commit`.
+
+The convention itself is documented in the skill, not here.
+Read [`skills/git-commit/SKILL.md`](skills/git-commit/SKILL.md)
+for the canonical version.
+
+## What this package is not
+
+- **Not a lint or hook enforcer.** The skill instructs; it
+  doesn't police. No `commit-msg` hook ships. Enforcement is
+  deferred until friction shows up.
+- **Not a branch / PR / rebase toolkit.** v0.1.0 ships *only*
+  the commit-message convention. Branch naming, PR templates,
+  and rebase discipline are v0.2.0+ candidates.
+- **Not a changelog generator.** Commits don't auto-write
+  changelog entries. That's `@cleepi/sdd`'s `/changelog`.
+  The link between commit and changelog is the ticket-id,
+  read by humans.
+- **Not configurable.** The Angular type set is fixed
+  (`feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`,
+  `chore`, `build`, `ci`, `revert`). Teams wanting extra types
+  edit a project-scope copy of the skill.
+- **Not opinionated about ticket trackers.** Ticket-id can be
+  `AC-NNN`, `LIN-NNN`, `gh-NN`, `DRAFT-NNN`, anything matching
+  `[A-Z]+-[0-9]+`. The skill doesn't validate.
+- **Not a hard dependency on `@cleepi/sdd`.** Soft-aware: when
+  sdd is loaded, the ticket-folder resolution chain matches
+  `/journal`'s. When sdd isn't loaded, the branch-name and
+  ask-user fallbacks still work.
+
+## Design at a glance
+
+```
+packages/git/
+  package.json
+  README.md
+  SPEC.md                        ← this file
+  CHANGELOG.md
+  skills/git-commit/SKILL.md     ← the canonical convention
+  prompts/commit.md              ← /commit
+```
+
+## The format (one-line summary)
+
+```
+<type>(<domain>): [<ticket-id> ]<message>
+```
+
+Subject line only. No body. No footers. **No `Co-authored-by:`.**
+See the skill for the full discipline.
+
+## Versioning
+
+Per-package SemVer. Pre-`1.0.0`, minor bumps may include
+breaking changes (per SemVer §4).
+
+## Related
+
+- [`skills/git-commit/SKILL.md`](./skills/git-commit/SKILL.md) —
+  canonical convention.
+- [CHANGELOG.md](./CHANGELOG.md) — release history.
+- Root cleepi [spec DRAFT-001](../../docs/DRAFT-001-cleepi-git-v0.1.0/spec.md) —
+  the v0.1.0 design rationale.
+- [`@cleepi/sdd`](../sdd/) — soft-aware sibling; `/commit`
+  shares ticket-resolution logic with `/journal`.

package/package.json

@@ -0,0 +1,39 @@
+{
+  "name": "@cleepi/git",
+  "version": "0.1.0",
+  "description": "Cleepi git conventions: conventional-commits skill + /commit prompt with monorepo-aware domain and ticket-id resolution. Subject-line-only commits; no body, no footers, no Co-authored-by ever.",
+  "keywords": [
+    "pi-package",
+    "cleepi",
+    "git",
+    "commit",
+    "conventional-commits",
+    "angular"
+  ],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/honzanemecek/cleepi.git",
+    "directory": "packages/git"
+  },
+  "bugs": "https://github.com/honzanemecek/cleepi/issues",
+  "homepage": "https://github.com/honzanemecek/cleepi/tree/main/packages/git#readme",
+  "publishConfig": {
+    "access": "public"
+  },
+  "pi": {
+    "skills": [
+      "./skills"
+    ],
+    "prompts": [
+      "./prompts"
+    ]
+  },
+  "files": [
+    "skills",
+    "prompts",
+    "SPEC.md",
+    "CHANGELOG.md",
+    "README.md"
+  ]
+}

package/prompts/commit.md

@@ -0,0 +1,199 @@
+---
+description: Craft and run a cleepi-style git commit. Resolves domain (from cwd) and ticket-id (from cwd → branch → ask), assembles the message, strips any Co-authored-by, and runs git commit.
+argument-hint: "<type> <message>"
+---
+
+The user wants to commit. Args: **$ARGUMENTS**
+
+## Critical: required tool calls BEFORE any commit
+
+The whole point of `/commit` is to assemble
+`<type>(<domain>): [<ticket-id> ]<message>`. You cannot do that
+without knowing cwd, staged paths, and branch name. **Therefore,
+before running `git commit`, you MUST run these tool calls—in
+this order—so resolution has data:**
+
+1. `bash: pwd`
+2. `bash: git diff --cached --name-only`
+3. `bash: git rev-parse --abbrev-ref HEAD`
+4. `bash: git status --porcelain`
+
+If you skip any of these you will produce a bare
+`feat: message` commit, which is a **resolution failure**, not
+a valid output. A `git commit` call without a preceding
+resolution trace from these four tool calls is a bug.
+
+Load `/skill:git-commit` if you haven't — it has the full
+convention, type table, anti-patterns, and hard rules.
+
+## Then: required output shape
+
+After the four tool calls, your reply MUST contain this block
+before the `git commit` call:
+
+```
+## Resolution
+- type: <type>            (from args)
+- domain: <domain>        (from cwd: <pwd-output>)
+- ticket-id: <id-or-none> (from <staged-paths|branch|args|none>)
+- message: <normalised-message>
+- assembled: <type>(<domain>): [<ticket-id> ]<message>
+```
+
+No exceptions. No "auto-confirm" mode skips this. No "just
+commit" shortens it. The user cannot inspect resolution they
+cannot see; the Resolution block must always appear.
+
+A `<type>: <msg>` shape commit (no `(<domain>)` clause) is a
+**resolution failure**. If you are about to produce one, STOP
+and walk resolution again.
+
+## Resolve the parts
+
+### 1. Type
+
+First word of `$ARGUMENTS` is the type. Validate against the
+Angular set (`feat`, `fix`, `docs`, `style`, `refactor`, `perf`,
+`test`, `chore`, `build`, `ci`, `revert`). If the first token
+isn't a valid type, **stop** and ask the user which type to use,
+quoting the type table.
+
+### 2. Domain
+
+Resolve from cwd:
+
+- If `cwd` is inside `packages/<n>/...`, domain = `<n>`.
+- Otherwise, **ask** the user: *"Domain? (free-form area name —
+  e.g. `meta`, `docs`, `ci`, `infra`, `release`)."*
+- If the user passed a `--domain=<x>` style override anywhere
+  in `$ARGUMENTS`, that wins.
+
+Don't use sub-areas of a package (`crew-agents`, `sdd-skill`).
+Use the package short name.
+
+### 3. Ticket-id
+
+Resolve in this order (manual override always wins):
+
+a. **Explicit token in `$ARGUMENTS`** matching `[A-Z]+-[0-9]+`
+   (excluding any token that's clearly part of the message).
+   If found, use it.
+
+b. **Ticket-id pattern in any staged file path.** Run
+   `git diff --cached --name-only` and grep the paths for
+   `(?:^|/)(<ticket-pattern>)-[^/]+/` where ticket-pattern is
+   `[A-Z]+-[0-9]+` or `DRAFT-[0-9]+`. Common matches:
+   `docs/AC-NNN-slug/...`, `packages/<n>/docs/AC-NNN-slug/...`.
+   If exactly one ticket-id matches across all staged paths,
+   use it. If multiple, list them and ask.
+
+c. **Ticket-id pattern visible in the working tree near the
+   change.** If (b) found nothing, check whether the parent
+   repo has a single recently-modified `docs/<ticket-id>-slug/`
+   folder (`ls -t docs/ packages/*/docs/ 2>/dev/null | head`)
+   that matches the type of change. Surface this as a
+   *candidate*, not an auto-pick — ask the user to confirm.
+
+d. **Git branch name.** Run `git rev-parse --abbrev-ref HEAD`.
+   Grep the result for `[A-Z]+-[0-9]+`. If matched, use the
+   first match.
+
+e. **Ask the user**: *"Ticket-id? (e.g. `AC-123`, or empty to
+   skip.)"* Include any candidates surfaced by (c) in the
+   question. If they leave it empty:
+
+   - For type `feat`/`fix`/`refactor`/`perf`: gently note that
+     a ticket-id is highly recommended for these; ask once more
+     if they want to provide one. If they still skip, proceed
+     without.
+   - For other types: proceed without.
+
+### 4. Message
+
+Everything in `$ARGUMENTS` after the type token, minus any
+extracted ticket-id token. Trim.
+
+Apply message style from the skill:
+
+- Imperative, present tense (`add`, not `added`/`adds`).
+- Lowercase first letter (after ticket-id if present).
+- No trailing period.
+- Target 50–72 chars total assembled length; hard cap 100.
+
+If the message clearly violates these (past tense, capitalized
+first word, trailing period), rewrite to match. Tell the user
+in your reply that you normalised it.
+
+## Check staging
+
+Run `git status --porcelain`. If there are unstaged changes:
+
+- Print the list of unstaged files.
+- Ask: *"Unstaged changes present. `[stage all / commit staged
+  only / cancel]`?"*
+- On `stage all`: run `git add -A` then continue.
+- On `commit staged only`: continue with whatever is currently
+  staged.
+- On `cancel`: stop. Don't commit.
+
+Never auto-`git add -A` without asking.
+
+## Assemble
+
+```
+<type>(<domain>): [<ticket-id> ]<message>
+```
+
+Examples (target shape):
+
+```
+feat(crew): AC-201 add reviewer pre-step
+docs(crew): fix README install path
+chore(meta): bump prettier
+```
+
+## Strip `Co-authored-by:` (hard rule)
+
+Before passing the message to `git commit`, scan it for any
+line matching `(?i)co-authored-by:`. **Remove the line and
+everything after it.** This rule overrides everything,
+including explicit user input that included such a line.
+
+Same for `Signed-off-by:`.
+
+If you removed anything, mention it in your reply: *"Stripped
+`Co-authored-by:` per the `git-commit` skill's hard rule."*
+
+## Confirm + commit
+
+Show the user:
+
+- The final assembled message (one line).
+- The resolution trace in one compact line: *"resolved:
+  domain=`X` (from cwd), ticket=`Y` (from <source>)"*. This
+  exists so the user can spot a wrong resolution before the
+  commit lands. Don't skip this even when the user said
+  "auto-confirm."
+- Brief summary of what's about to be committed: file count, a
+  sample of paths from `git diff --cached --name-only`.
+
+Ask: *"Commit? `[y / N / edit]`"*
+
+- `y`: run `git commit -m "<assembled-message>"`. Report the
+  resulting commit hash and short summary.
+- `edit`: ask the user what to change; re-assemble; re-confirm.
+- `N` (default): stop. Don't commit.
+
+If the user pre-authorised auto-confirmation, treat that as
+standing consent for the *confirm step only* — still show the
+resolution trace so wrong resolutions are visible after the fact.
+
+## Discipline check
+
+If at any point you almost wrote a multi-line commit, almost
+included `Co-authored-by:`, or almost used a type outside the
+Angular set, **stop and reload the skill**. These mistakes are
+the exact reason this prompt exists.
+
+Be concise throughout. No throat-clearing in your reply. The
+user wants the commit done, not a summary of what you did.

package/skills/git-commit/SKILL.md

@@ -0,0 +1,212 @@
+---
+name: git-commit
+description: Cleepi's commit-message convention. Conventional Commits + AngularJS types, with monorepo-aware domain (package short name), optional ticket-id, subject-line only (no body, no footers, NEVER Co-authored-by). Load when about to write a git commit message in a cleepi-style repo, or when asked about commit conventions.
+---
+
+# git-commit
+
+You are about to write a git commit message in a cleepi-style
+repo. Follow this convention exactly. The rules below are not
+suggestions.
+
+## The format
+
+```
+<type>(<domain>): [<ticket-id> ]<message>
+```
+
+Examples (the only shape you produce):
+
+```
+feat(crew): AC-201 add reviewer pre-step
+refactor(sdd): AC-202 collapse Why-now into Why
+docs(crew): fix README install path
+chore(meta): bump prettier
+fix(atlassian): DRAFT-007 handle empty JQL response
+test(git): cover ticket-id detection
+build(crew): pin pi-subagents to 0.25.0
+ci(meta): run smoke tests on pull request
+revert(sdd): undo phase-3 AGENTS.md change
+```
+
+Real `git log` from a cleepi repo should read as a clean list
+of one-liners like the above. No multi-line messages anywhere.
+
+## Hard rules
+
+These are non-negotiable. AI tooling and humans both break them.
+The skill exists to stop that.
+
+- **Subject line only.** One line. No body. No footers.
+- **NEVER `Co-authored-by:`.** Not for AI assistants. Not for
+  pair programmers. Not for "credit." If your tooling tries to
+  append one, **strip it before committing.** This is a hard
+  rule, not a preference.
+- **No `Signed-off-by:`** either. Same reason. The skill doesn't
+  ship a DCO workflow; commits stay clean.
+- **No emoji, no decorations.** `feat(crew):` not `✨ feat(crew):`.
+- **No breaking change footer.** If a change is breaking, use
+  the bang syntax (`feat(crew)!: ...`) and put the *rationale*
+  in the spec, not in the commit.
+- **No trailing period** on the subject line.
+- **Imperative, present tense, lowercase first letter** of the
+  message after the colon (or after the ticket-id if present).
+  "add x," not "Adds x" or "Added x" or "Add x.".
+
+## Types
+
+Fixed AngularJS / Conventional Commits set. No extension via
+config; teams wanting other types edit a project-scope copy of
+this skill.
+
+| Type | Use for |
+|---|---|
+| `feat` | New feature or user-visible capability |
+| `fix` | Bug fix |
+| `docs` | Documentation only (README, comments, skill files) |
+| `style` | Formatting, whitespace, no code semantics change |
+| `refactor` | Code change that's neither feat nor fix |
+| `perf` | Performance improvement |
+| `test` | Adding or fixing tests |
+| `chore` | Build glue, deps, tooling that's neither ci nor build |
+| `build` | Build system, package config, dependency bumps |
+| `ci` | CI config, workflows, automation |
+| `revert` | Reverting a previous commit |
+
+If you can't pick between two types, prefer the more specific
+one. `feat` is overused; if the change is an internal cleanup,
+it's `refactor`, not `feat`.
+
+## Domain
+
+In a cleepi-style monorepo, **domain = the affected package's
+short name** (`crew`, `sdd`, `git`, `atlassian`, `coding`,
+`base`, etc.). One package per commit. If a change spans two
+packages, split into two commits.
+
+Outside the `packages/` tree, domain is a free-form feature
+area:
+
+- `meta` — repo-level meta files (root README, root CHANGELOG,
+  AGENTS.md, CONSTITUTION.md)
+- `docs` — repo-level docs/ and specs (when not tied to a
+  package)
+- `ci` — repo-level CI config
+- `infra` — infra-as-code, deployment glue
+- `release` — release prep, version bumps, tags
+
+Don't use sub-areas of a package as the domain (`crew-agents`
+or `sdd-skill`). Use the package name (`crew`, `sdd`); the
+commit message says what changed.
+
+## Ticket-id
+
+**Highly recommended. Not required.**
+
+Format: `[A-Z]+-[0-9]+`. Cleepi ticket prefixes include
+`AC-NNN` (Atlassian), `LIN-NNN` (Linear), `gh-NN` (GitHub
+issue), `DRAFT-NNN` (pre-tracker work that's still spec'd).
+
+When present, the ticket-id sits **directly after the colon**,
+single space before the message:
+
+```
+feat(crew): AC-201 add reviewer pre-step
+```
+
+NOT `[AC-201]`, NOT `(AC-201)`, NOT `AC-201:`. Just the bare
+token, then space, then message.
+
+When omitted (small chores, typos, doc tweaks):
+
+```
+docs(crew): fix README install path
+chore(meta): bump prettier
+```
+
+The skill won't fail a commit for missing ticket-id, but it
+will gently flag the omission for `feat`/`fix`/`refactor`/`perf`
+commits, since those are the ones that should anchor on a
+spec'd ticket.
+
+## Message style
+
+- **Imperative, present tense.** "add X," "fix Y," "remove Z."
+  Not "added," "fixes," "removing."
+- **Lowercase first letter** of the message (after the ticket-id
+  if present). Acronyms and proper nouns stay cased.
+- **No trailing period.**
+- **Concise but specific.** "fix bug" is useless. "fix off-by-one
+  in pagination" is a commit message.
+- **Around 50–72 characters total** is the target. Hard cap 100.
+- **No "and"** if you can avoid it. "feat(crew): add X and refactor
+  Y" → two commits.
+
+## Anti-patterns (don't do these)
+
+| ❌ Bad | ✓ Good | Why |
+|---|---|---|
+| `feat: add reviewer` | `feat(crew): AC-201 add reviewer pre-step` | Missing domain, ticket, specificity. |
+| `Update README` | `docs(crew): fix install path in README` | No type, no domain, vague. |
+| `feat(crew): Added reviewer.` | `feat(crew): AC-201 add reviewer pre-step` | Past tense + trailing period + missing ticket. |
+| `feat(crew-agents): add reviewer` | `feat(crew): AC-201 add reviewer pre-step` | Domain is package, not sub-area. |
+| `feat(crew): AC-201 add reviewer\n\nCo-authored-by: Claude` | `feat(crew): AC-201 add reviewer pre-step` | Subject-line only. NEVER Co-authored-by. |
+| `feat(crew): ✨ add reviewer` | `feat(crew): add reviewer pre-step` | No emoji. |
+| `feat(crew,sdd): cross-package change` | `feat(crew): ...` + `feat(sdd): ...` | Split into two commits. |
+| `wip: stuff` | (don't commit yet, or `chore(<domain>): wip <specific>`) | "wip" as type isn't in the set. If you must, use `chore` and be specific. |
+
+## Resolution chain for `/commit`
+
+When invoked via the `/commit` slash command, the prompt resolves
+context in this order (manual args always win):
+
+1. **Type** — first arg to `/commit`. Required. Validated against
+   the type table above.
+2. **Domain** — nearest `packages/<n>/` ancestor of cwd → package
+   short name. Outside packages, prompt asks (or accepts a
+   free-form arg).
+3. **Ticket-id** — explicit token in args → ticket-id pattern in
+   any **staged file path** (e.g. `docs/AC-NNN-slug/...`) →
+   candidate surfaced from recently-modified `docs/<ticket>-slug/`
+   folders in the repo (asks for confirmation, never auto-picks)
+   → git branch name (grep `[A-Z]+-[0-9]+`) → ask user.
+
+   This differs from `@cleepi/sdd`'s `/journal` chain because
+   `/commit` runs from inside *code*, not the ticket folder.
+   `/journal` walks up from cwd; `/commit` reads staged paths
+   and branch name instead.
+4. **Message** — remaining args to `/commit`.
+5. **Co-authored-by strip** — defence-in-depth: scan the
+   assembled message for any `Co-authored-by:` line and remove
+   it before passing to `git commit`. This rule overrides
+   everything else, including the user's explicit input.
+
+**Resolution is non-skippable.** Even when the user says "just
+commit" or auto-confirms, type/domain/ticket-id resolution
+still runs. The user can skip the *confirmation* step; they
+cannot skip resolution. A bare `feat: <msg>` commit is a
+resolution failure, not a valid output.
+
+## Voice and length
+
+The skill mirrors the `@cleepi/sdd` discipline:
+
+- **Concise.** Cleepi commits are one-liners. So is the message.
+- **Specific.** "fix bug" is not a commit message; it's a
+  shrug. Name the thing.
+- **No filler.** "Various improvements" → no. List the actual
+  changes in separate commits.
+- **Imperative.** Read the message after "If applied, this
+  commit will…" — it should fit naturally.
+
+If you cannot describe a change as one specific imperative line
+under ~70 characters, the commit is too big. Split it.
+
+## When the user disagrees
+
+If the user wants a body, footer, or `Co-authored-by:`, push
+back once with a one-liner referencing this skill. If they
+insist, **don't comply silently** — instead, write the message
+their way *and* add a one-line note in your reply that you
+overrode the cleepi convention at their explicit request.
+That way the next session sees the deviation logged.