commit

Installation
SKILL.md

Commit

  1. Inspect the working tree and diffs. If there's nothing worth committing, or the diff isn't understood, stop.
  2. Stage only the intended files, not broad adds.
  3. Use the user's message if provided. Otherwise write a Conventional Commit matching the repo's existing style: imperative subject, add a body only when the reason or risk matters.
  4. Commit and report the hash and message.

Rules

  • Never commit .env, credentials, or keys.
Installs
308
GitHub Stars
210
First Seen
Apr 13, 2026
commit — owainlewis/blueprint