agentleFS
Sign inStart free
StormixStormix/transcripts-mcp/.agents/skills/commit/SKILL.md

commit

Skill8 starsChanged 2 months agoMITView on GitHub

Commit Staged Changes

188 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use validate-plan, act-on-feedback and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • shawn-dumasSkill

    validate-plan

    Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.

    Also in 5 projects that use this

  • MicrosoftSkill

    act-on-feedback

    Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

    Also in 3 projects that use this

  • decocmsSkill

    add-mcp-tools

    Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration

    Also in 3 projects that use this

  • MicrosoftSkill

    generate-run-commands

    Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

    Also in 3 projects that use this

  • mitsuhikoSkill

    oebb-scotty

    Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

    Also in 3 projects that use this

  • mitsuhikoSkill

    pi-share

    Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Branch: Commit on the current branch.

    line 11
  2. Distinctive:

    Run the single git command from git-conventions to gather all context:

    line 17
  3. Distinctive:

    After committing, show the commit hash and confirm success.

    line 60
  4. Distinctive:

    If the commit fails (e.g., commitlint validation fails):

    line 64
  5. Very specific:

    Follow the conventional commits format: <type>(<scope>): <subject>

    line 72
  6. Distinctive:

    Use imperative, present tense for subject and body

    line 73
  7. Distinctive:

    Run single git command to gather context

    line 84

“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Commit Staged Changes

Generate a conventional commit message and commit staged changes, respecting the project's commitlint configuration.

Branch: Commit on the current branch. Do not create or switch to a feature branch unless the user asks (see git-conventions — Current branch (agents)).

Instructions

1. Gather Context

Run the single git command from git-conventions to gather all context:

echo "=== BRANCH ===" && git rev-parse --abbrev-ref HEAD && echo "=== STAGED FILES ===" && git diff --staged --stat && echo "=== STAGED CHANGES ===" && git diff --staged

2. Analyze & Generate

From the gathered information:

  • Extract the GitHub issue number if available from branch name or changes
  • Identify affected packages/apps from file paths → determine scope
  • Analyze the nature of changes → determine commit type
  • Generate commit message following the format in git-conventions

3. Present & Execute

Show the generated commit message in a code block:

type(scope): description

Optional body text

Closes #123

Explain the ticket number, type, and scope chosen.

Then execute the commit:

For commits with body:

git commit -m "type(scope): description" -m "Body paragraph" -m "Closes #GITHUB_ISSUE"

For commits without body:

git commit -m "type(scope): description"

After committing, show the commit hash and confirm success.

4. Error Handling

If the commit fails (e.g., commitlint validation fails):

  • Show the error message
  • Explain what went wrong
  • Suggest how to fix it or offer to generate a new message

Key Points

  • Follow the conventional commits format: <type>(<scope>): <subject>
  • Use imperative, present tense for subject and body
  • Body is optional unless adding context or breaking changes
  • Footer with Closes #123 is optional but recommended for feat/fix commits
  • See git-conventions for complete format rules

Example Usage

User: "commit", "commit staged changes", or /commit

Response:

  1. Run single git command to gather context
  2. Extract ticket number, analyze changes, determine type and scope
  3. Generate properly formatted commit message
  4. Show the message in a code block
  5. Execute the git commit command
  6. Confirm success with commit hash

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free