agentleFS
Sign inStart free
avihaymenahemavihaymenahem/velo/.claude/skills/commit/SKILL.md

commit

Skill715 starsChanged 9 months agoApache-2.0View on GitHub

Create a conventional commit and push to the current branch. Ensures commit messages follow the Conventional Commits spec for automatic versioning with release-please.

  • Commits and pushes

188 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

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a git commit following the Conventional Commits specification.

    line 9
  2. Distinctive:

    Keep the first line under 72 characters

    line 45

“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

Conventional Commit

Create a git commit following the Conventional Commits specification. This is required for release-please to auto-determine version bumps.

Steps

  1. Check the current state — run git status (no -uall flag) and git diff --staged to understand what's being committed. If nothing is staged, stage the relevant files (prefer specific files over git add .).

  2. Determine the commit type from the changes:

    TypeWhen to useVersion bump
    featNew feature or capabilityminor (0.x.0)
    fixBug fixpatch (0.0.x)
    docsDocumentation onlyno release
    styleFormatting, whitespace, semicolons (no logic change)no release
    refactorCode restructuring (no feature/fix)no release
    perfPerformance improvementpatch (0.0.x)
    testAdding or fixing testsno release
    buildBuild system, dependencies, CIno release
    choreMaintenance, tooling, configsno release
    ciCI/CD pipeline changesno release
    revertReverting a previous commitdepends on reverted type

  3. Format the commit message strictly as:

    type(scope): short description

Optional longer body explaining the "why" (not the "what").

BREAKING CHANGE: description (if applicable)

    Rules:

    • type is required, lowercase
    • scope is optional but encouraged — use the affected area (e.g., composer, sync, settings, db, ui, ai, calendar, auth, search, shortcuts, tray, notifications, labels, filters, queue, imap, attachments)
    • description starts lowercase, no period at end, imperative mood ("add" not "added")
    • BREAKING CHANGE footer triggers a major version bump — use sparingly
    • Keep the first line under 72 characters
  4. Examples:
    feat(composer): add scheduled send with date picker
fix(sync): handle expired Gmail history token gracefully
refactor(db): consolidate migration helpers
docs: update keyboard shortcuts table in CLAUDE.md
chore(ci): add release-please workflow
perf(search): use FTS5 trigram index for faster lookups
feat(ai)!: switch to streaming responses

BREAKING CHANGE: AI provider interface now requires stream() method
  5. Create the commit using a HEREDOC for proper formatting:
    git commit -m "$(cat <<'EOF'
type(scope): description
EOF
)"
  6. Push to the current branch with git push. If the branch has no upstream, use git push -u origin HEAD.

User hint

$ARGUMENTS

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