# 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