agentleFS
alamenaialamenai/terrae/.claude/skills/commit/SKILL.md

commit

Skill245 starsChanged 9 months agoMITView on GitHub

Create standardized git commits following Terrae's conventions

  • Reads credentials

187 other projects use a version of this.

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

12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create standardized git commits following Terrae's conventions.

    line 9
  2. Distinctive:

    Run git status to see changed files

    line 14
  3. Distinctive:

    Run git diff to see the actual changes

    line 15
  4. Distinctive:

    Ask the user if they want to proceed with the commit

    line 20
  5. Distinctive:

    Never stage sensitive files (.env, credentials, etc.)

    line 24
  6. Distinctive:

    When committing a new component, split into 3 separate commits in this order:

    line 49
  7. Very specific:

    Do NOT add Co-Authored-By lines

    line 57
  8. Distinctive:

    Do NOT commit until user approves

    line 58
  9. Very specific:

    Do NOT use --amend unless explicitly requested

    line 59
  10. Distinctive:

    Do NOT push unless explicitly requested

    line 60
  11. Distinctive:

    Keep commit messages concise (under 72 characters)

    line 61
  12. Distinctive:

    Run git status to confirm commit succeeded

    line 70

“Common” is measured: kept by at least 6 in 10 of the 167 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 Skill

Create standardized git commits following Terrae's conventions.

Instructions

  1. Check Current State
    • Run git status to see changed files
    • Run git diff to see the actual changes
  2. Review Changes with User
    • Summarize what files were changed
    • Explain the nature of changes (new feature, bug fix, refactor, etc.)
    • Ask the user if they want to proceed with the commit
  3. Stage Files
    • Stage specific files by name (avoid git add -A or git add .)
    • Never stage sensitive files (.env, credentials, etc.)
  4. Commit Message Format Follow conventional commits:

    type(scope): description

    Types:

    • feat: New feature
    • fix: Bug fix
    • docs: Documentation changes
    • style: Formatting, no code change
    • refactor: Code restructuring
    • test: Adding or updating tests
    • chore: Maintenance tasks

    Examples:

    • feat(marker): add rotation support
    • fix(popup): prevent memory leak on unmount
    • docs(readme): update installation instructions
  5. New Component Convention

    When committing a new component, split into 3 separate commits in this order:

    1. feat(map): add {component} component — the source file (src/registry/map/{slug}.tsx)
    2. feat(docs): add {component} example components — all example files (src/app/docs/_components/examples/{slug}-*.tsx)
    3. feat(docs): add {component} documentation page — the docs page (src/app/docs/{slug}/page.tsx)

    Shared file modifications (sidebar, components page, changelog, registry.json, barrel export) should be committed separately since they often contain changes for multiple components.

  6. Important Rules
    • Do NOT add Co-Authored-By lines
    • Do NOT commit until user approves
    • Do NOT use --amend unless explicitly requested
    • Do NOT push unless explicitly requested
    • Keep commit messages concise (under 72 characters)
  7. Create the Commit

    git commit -m "type(scope): description"
  8. Verify
    • Run git status to confirm commit succeeded
    • Show the commit hash to the user

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.