commit-hygiene

Files (1)

• SKILL.md

SKILL.md (first lines)

## When to Use

Use this skill when:
- Creating commits
- Reviewing commit history in a PR
- Cleaning up staged changes before commit

## Rules

1. Use the repository commit format: `<type>(<scope>): <description>`.
2. Keep one logical change per commit.
3. The message should explain why, not only what changed.
4. Do not commit generated, temporary, local, or secret-bearing artifacts.
5. Do not hide unrelated refactors inside a bug fix or feature commit.
6. Before mutating work or creating/reviewing commits, report branch state from `git status --short --branch`.
7. Report pending commits against the remote base, using `git log --oneline origin/main..HEAD` when applicable.
8. State the branch decision explicitly: continue current branch, create a new branch, or open PR before continuing.
9. If the branch has more than 5 unmerged commits, recommend opening a PR and continuing new work on a fresh branch.
10. When the resolved project declares `commit_identity_policy`, verify both
    author and committer identities before commit and run the canonical
    introduced-range checker before PR approval. Do not infer this policy from
    a folder name.
11. A noncompliant published commit must be reported, not rewritten
    automatically. Rewriting requires explicit user authorization and
    `--force-with-lease`.

## Pre-Commit Checklist

- [ ] Branch state was checked with `git status --short --branch`
- [ ] Pending commit count was checked against the remote base
- [ ] Branch decision is explicit: continue, create branch, or open PR
- [ ] Diff matches the commit scope
- [ ] No secrets, tokens, or credentials
- [ ] No cache, coverage, build, or scratch artifacts
- [ ] Relevant tests or checks for the change were run
- [ ] Commit message is clear and scoped
- [ ] Project-scoped author and committer identity policy passes, when declared

From cheetah-alo/NegritaOS, Apache-2.0.

More from cheetah-alo/NegritaOS