Claude Cursor Skill

commit

Commit all changes on the current branch, main included.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download svyatov-supermatt-skills_commit-6b893bc.zip · 1 KB

Install

skills CLI npx skills add https://github.com/svyatov/supermatt/tree/main/skills/commit
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install svyatov-supermatt@llmmart
Git git clone https://github.com/svyatov/supermatt.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole svyatov/supermatt collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Commit every change in the working tree on the current branch. Do not switch or create a branch, even on main. The arguments, if any, are a hint at what the change is about, not the message itself.

  1. Run git status --short --branch --untracked-files=all. When HEAD exists, run git diff HEAD --stat and git log --oneline -10, then read the full diff (git diff HEAD). For an initial commit with no HEAD, read git diff --cached for staged additions and git diff for their unstaged changes; there is no history to inspect. In either case, read every untracked file, including files inside new directories, before writing anything.
  2. Scan it for credentials, tokens, private keys, and any value that does not belong in this repository. If you find one, stop, commit nothing, and report what you found.
  3. An untracked directory that holds a local tool's state (an index, cache, or database, such as .codegraph/) belongs in the root .gitignore, even when it ships its own .gitignore: add its path there, commit that line with the rest, and say so in the report.
  4. Stage the changes. Prefer explicit paths over git add -A.
  5. Write a Conventional Commit type(scope): description, matching the subject style in git log when history exists. When the oss-writing skill is installed, load and follow it through the host's skill mechanism for the wording.
  6. Commit. Report the subject and the short hash, plus the .gitignore line from step 3 if you added one, nothing else.

Split into several commits when the diff covers unrelated changes.

Files (supermatt)
  • agents
    • openai.yaml 154 B
      Loading…
  • SKILL.md 1.7 KB
    ---
    name: commit
    description: "Commit all changes on the current branch, main included."
    argument-hint: "[message hint]"
    disable-model-invocation: true
    license: MIT
    ---
    
    Commit every change in the working tree on the current branch. Do not switch or create a branch, even on main. The arguments, if any, are a hint at what the change is about, not the message itself.
    
    1. Run `git status --short --branch --untracked-files=all`. When `HEAD` exists, run `git diff HEAD --stat` and `git log --oneline -10`, then read the full diff (`git diff HEAD`). For an initial commit with no `HEAD`, read `git diff --cached` for staged additions and `git diff` for their unstaged changes; there is no history to inspect. In either case, read every untracked file, including files inside new directories, before writing anything.
    2. Scan it for credentials, tokens, private keys, and any value that does not belong in this repository. If you find one, stop, commit nothing, and report what you found.
    3. An untracked directory that holds a local tool's state (an index, cache, or database, such as `.codegraph/`) belongs in the root `.gitignore`, even when it ships its own `.gitignore`: add its path there, commit that line with the rest, and say so in the report.
    4. Stage the changes. Prefer explicit paths over `git add -A`.
    5. Write a Conventional Commit `type(scope): description`, matching the subject style in `git log` when history exists. When the `oss-writing` skill is installed, load and follow it through the host's skill mechanism for the wording.
    6. Commit. Report the subject and the short hash, plus the `.gitignore` line from step 3 if you added one, nothing else.
    
    Split into several commits when the diff covers unrelated changes.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.