agentsclimarketplace
Sign in

Tenzir commit changes

Skill tenzir/skills/skills/tenzir-commit-changes

Commit changes as clean, reviewable snapshots. Use when committing, staging, splitting work into logical units, writing or fixing commit messages, creating fixup commits, or cleaning up commit history. Also use when the user says "commit this", "save my changes", "make a commit", or "write a better commit message."From its SKILL.md

Install
npx -y skills add tenzir/skills --skill tenzir-commit-changes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, as published. Nobody here has run it

Commit Changes

Commit changes as clean, reviewable snapshots.

Workflow

  1. Read git status and the relevant diffs before deciding how many commits to make.
  2. Split orthogonal work into separate logical units. If a file mixes unrelated edits, stage only the hunks for the current commit.
  3. Run the relevant checks before committing. If you skip a check, say so.
  4. For each commit:
    • Stage only the relevant hunks.
    • Read the staged diff before writing the message.
    • Write the commit message from what is actually staged.
    • Create the commit with a real multiline message, using separate -m arguments for each message section.
    • Do not put literal \n escapes in a single -m string.
    • Amend immediately if the final message reads awkwardly.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.