agentleFS
Sign inStart free
finosfinos/git-proxy/.agents/skills/commit/SKILL.md

commit

Skill262 starsChanged 2 months agoApache-2.0View on GitHub

Create a conventional commit for the current staged/unstaged changes

We split this skill into the rules it gives an agent

12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 11

    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:

    Create a git commit for the current staged/unstaged changes using Conventional Commits.

    line 6
  2. Distinctive:

    Read AGENTS.md first. It is the canonical project guide for this repository.

    line 8
  3. Distinctive:

    Run git status and git diff to understand what changed

    line 12
  4. Distinctive:

    Write a commit message following Conventional Commits format

    line 14
  5. Very specific:

    Use --signoff to sign off using the committer's git config (do NOT hardcode any name/email)

    line 15
  6. Distinctive:

    Do NOT add Co-Authored-By or any other trailers beyond Signed-off-by

    line 16
  7. Distinctive:

    If there are no changes, say so and stop

    line 17
  8. Distinctive:

    Do NOT capitalize the first letter after the type prefix

    line 33
  9. Distinctive:

    Do NOT end with a period

    line 34
  10. Distinctive:

    Keep under 72 characters total

    line 35
  11. Distinctive:

    Use long multi-line messages for simple changes

    line 61
  12. Distinctive:

    Use past tense ("added", "fixed")

    line 63

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

Create a git commit for the current staged/unstaged changes using Conventional Commits.

Read AGENTS.md first. It is the canonical project guide for this repository.

Rules:

  1. Run git status and git diff to understand what changed
  2. Stage relevant files (prefer specific files over git add -A)
  3. Write a commit message following Conventional Commits format
  4. Use --signoff to sign off using the committer's git config (do NOT hardcode any name/email)
  5. Do NOT add Co-Authored-By or any other trailers beyond Signed-off-by
  6. If there are no changes, say so and stop

Commit format:

<type>[optional scope]: <description>

Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore

Scope (optional): a noun describing the affected area in parentheses. Common scopes: config, api, proxy, db, e2e, docker, ci.

Subject line rules:

  • Imperative mood ("add", not "added" or "adds")
  • Do NOT capitalize the first letter after the type prefix
  • Do NOT end with a period
  • Keep under 72 characters total

For breaking changes, add ! after the type/scope:

feat(config)!: rename queue config key

Examples of good messages:

  • "feat(api): add support for rejection reason"
  • "fix(config): handle invalid regex on commitConfig"
  • "refactor(ts): remove any/as usages in push-actions"
  • "test(proxy): add tests for Git hosts other than GitHub"
  • "docs: update architecture diagram in Architecture.md"
  • "build: bump express to 5.2.1"
  • "chore: remove unused import in services/push.ts"

Commit command:

git commit --signoff -m "<type>[scope]: <description>"

Do NOT:

  • Use long multi-line messages for simple changes
  • Add Co-Authored-By trailers
  • Use past tense ("added", "fixed")
  • Hardcode any author name or email
  • Omit the type prefix

Download now (ZIP)

  • Other versions189 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 189

    1. microsoft/vscode★ 194ksame name
    2. TryGhost/Ghost★ 56ksame name
    3. ToolJet/ToolJet★ 41ksame name
    4. ShareX/ShareX★ 41ksame name
    5. openai/symphony★ 27ksame name
    6. ccusage/ccusage★ 19ksame name
    7. ryoppippi/ccusage★ 19ksame name
    8. windmill-labs/windmill★ 18ksame name
    9. EverMind-AI/EverOS★ 14ksame name
    10. EverMind-AI/EverMemOS★ 14ksame name

    179 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects 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

    • decocmsSkill

      run-local-freestyle

      Run Studio locally with chats and task runs executing in real Freestyle sandboxes, reachable through an ngrok tunnel. Use when asked to "run locally with Freestyle", "test claude-code chats locally", "run the sandbox harness end to end", or to try daemon/harness-runner changes in a real sandbox.

      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

  • In this repository10 other files it gives its agents.

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