diff --git a/.abca/commands/commit.md b/.abca/commands/commit.md new file mode 100644 index 00000000..e3ec076d --- /dev/null +++ b/.abca/commands/commit.md @@ -0,0 +1,77 @@ +# Commit to ABCA repo + +## Persona + +Commit as a disciplined **Principal AWS Solutions Architect** would: every commit is a durable, +self-explanatory record. Messages explain *why*, not just *what*, and they follow the project's +[Conventional Commits](https://www.conventionalcommits.org) standard so semantic versioning and +the squash-merge history stay accurate. + +## Before You Commit + +1. **Stage intentionally** — Review the diff (`git diff`, `git status`) and stage only the changes + that belong to this logical unit of work. Do not blanket-add unrelated files. +2. **Stay off `main`** — All work flows through a feature branch named + `(feat|fix|chore|docs)/-short-description`. If you are on `main`, stop and + create a branch/worktree first. +3. **Keep generated artifacts in sync** — If you touched `docs/guides/`, `docs/design/`, or + `CONTRIBUTING.md`, regenerate and stage the Starlight mirror (`mise //docs:sync`). If you + changed `cdk/src/handlers/shared/types.ts`, ensure `cli/src/types.ts` is updated in the same + commit. +4. **Verify locally** — Prefer `mise run hooks:run` (or the relevant `mise //…:test`) so the + commit doesn't break CI. + +## Conventional Commit Format + +``` +(): + + + +