mcpField
C
commit-changes

commit-changes

github.com/tldrawDevelopment51.1k55 installsUpdated today
Repository

About commit-changes

commit-changes is a coding skill for creating a focused git commit from current changes. It guides status and diff review, selective staging, and conventional commit messages while prohibiting pushes and AI attribution.

Key features

  1. 01Review branch, status, diffs, and recent commits
  2. 02Inspect changed files before committing
  3. 03Stage relevant files while avoiding secrets
  4. 04Write conventional commit messages
  5. 05Do not push or amend by default

Use cases

  1. 01Commit a focused set of working-tree changes
  2. 02Check staged and unstaged changes before committing
  3. 03Keep credentials out of a commit

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tldraw/tldraw --skill commit-changes

After installing, type/commit-changesin Claude Code to confirm it loaded.

Details

From the project README

Commit changes

Create a focused git commit for the current changes.

Workflow

  1. Gather context:
    • User notes, if provided.
    • Current branch: git branch --show-current.
    • Working tree: git status --short.
    • Staged changes: git diff --cached --stat.
    • Unstaged changes: git diff --stat.
    • Recent commits for style reference: git log -5 --oneline.
  2. Review the changed files.
  3. If there are no changes to commit, tell the user and stop.
  4. If there are unstaged changes, stage the relevant files with git add.
  5. Do not stage files that look like secrets, credentials, API keys, or private environment files.
  6. Write a conventional commit message:
type(scope): brief description

Optional longer explanation if the changes are complex.

Allowed types: feat, fix, refactor, test, docs, chore, perf, style, build, ci.

Message guidelines

  • Keep the first line under 72 characters.
  • Use imperative mood, for example add feature, not added feature.
  • Be specific about what changed and why.
  • Incorporate user-provided context when it clarifies intent.

Commit rules

  • Use git commit -m "message".
  • Do not push.
  • Do not amend unless explicitly requested.
  • Do not use --no-verify.
  • Do not include AI attribution.

If the commit fails because of hooks, fix mechanical formatting, lint, or import issues and retry. If the hook failure reveals a meaningful product or implementation issue, stop and ask the user how to proceed.

Comments

Markdown supported