agentleFS
Sign inStart free
decocmsdecocms/studio/.claude/skills/commit/SKILL.md

commit

Skill415 starsChanged 3 months agoMITView on GitHub

Prepare code for review by running quality checks, creating conventional commits, and opening pull requests. Use when the user wants to commit changes, create a PR, prepare for code review, or asks to commit their work.

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you're on the main branch, create a new feature branch first before making any commits.

    line 10
  2. Distinctive:

    Run the following commands in order:

    line 13
  3. Distinctive:

    If any checks fail, address the issues before proceeding.

    line 20
  4. Distinctive:

    Use types: feat, fix, refactor, docs, chore, test, etc.

    line 25
  5. Very specific:

    Use the gh CLI tool to create or update the PR.

    line 30
  6. Very specific:

    Read .github/pull_request_template.md and follow its structure exactly

    line 33
  7. Distinctive:

    Ensure the PR title follows Conventional Commit format

    line 37

“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

I'm getting ready for code review. Please follow these steps:

0. Branch Check

If you're on the main branch, create a new feature branch first before making any commits.

1. Quality Assurance Checks

Run the following commands in order:

  1. bun run fmt
  2. bun run lint
  3. bun run check:ci
  4. bun run knip
  5. bun test

If any checks fail, address the issues before proceeding.

2. Create Commits

Split the file changes into logical commits following Conventional Commit format:

  • type(scope): message (e.g., feat(chat): add thread deletion, fix(auth): resolve token expiry)
  • Use types: feat, fix, refactor, docs, chore, test, etc.

Push all commits to the remote branch.

3. Create or Update Pull Request

Use the gh CLI tool to create or update the PR. The PR description MUST follow the structure defined in .github/pull_request_template.md.

Important:

  • Read .github/pull_request_template.md and follow its structure exactly
  • Analyze the git diff and commits to generate accurate content for each section
  • For "How to Test", provide specific, actionable steps based on the actual changes
  • Mark "N/A" for Screenshots and Migration Notes if not applicable
  • Ensure the PR title follows Conventional Commit format

4. Report Results

Finally, report the GitHub PR URL.

Download now (ZIP)

  • Other versions189 projects use a version of this.

    Word for word · 2

    1. decocms/admin★ 409100% same
    2. decocms/mesh★ 409100% same

    Edited · 0

    None found.

    Wrote their own version · 187

    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. ryoppippi/ccusage★ 19ksame name
    7. ccusage/ccusage★ 19ksame name
    8. windmill-labs/windmill★ 18ksame name
    9. EverMind-AI/EverOS★ 14ksame name
    10. EverMind-AI/EverMemOS★ 14ksame name

    177 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 act-on-feedback, generate-run-commands and 8 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.
    • 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

    • 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

    • OpenAISkill

      pull

      Also in 8 projects that use this

    • skilluseSkill

      epic

      Create and manage Epics - collections of related issues for major feature areas. Use when starting a new project(big feature), organizing work into themes, or adding reference documents.

      Also in 3 projects that use this

  • In this repository4 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