agentleFS
Sign inStart free
typeweavertypeweaver/skills/skills/engineering/conventional-commit/SKILL.md

conventional-commit

Skill2 starsChanged 53 days agoMITView on GitHub

Create Conventional Commits from completed changes.

  • Reads credentials

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use shipping-and-launch, doubt-driven-development 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.
  • LLl0k0laDSkill

    shipping-and-launch

    Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

    Also in 3 projects that use this

  • seikaikyoSkill

    doubt-driven-development

    對非平凡決策啟動新鮮 context 對抗審查（找碴不背書），在修正還便宜的時候抓出錯誤方向。適用：高風險改動（production、資安敏感邏輯、不可逆操作）、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。

    Also in 3 projects that use this

  • LLl0k0laDSkill

    api-and-interface-design

    Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

    Also in 3 projects that use this

  • HK-hubSkill

    code-simplification

    Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

    Also in 3 projects that use this

  • guaderramaSkill

    spec-driven-development

    Generate comprehensive specifications for software projects using spec-driven development methodology. Leverages Bright Data MCP tools to research documentation, analyze competitor implementations, gather real-world examples, and enrich specs with architectural insights. Use when user requests specifications, technical plans, project specs, or architecture documentation.

    Also in 3 projects that use this

  • MicrosoftSkill

    api-design

    Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

    Also in 3 projects that use this

  • +1 more from LLl0k0laD

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 11 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Create the commits and stop there.

    line 11
  2. Distinctive:

    Read every changed file's staged and unstaged diff before deciding what belongs together.

    line 15
  3. Very specific:

    Before staging, scan both diffs for credentials, tokens, private keys, .env contents, and internal hostnames the repository does not …

    line 18
  4. Distinctive:

    Do not use git add -A, git add ., or git commit -a.

    line 23
  5. Distinctive:

    Commit, then read git show to confirm the contents and message.

    line 25
  6. Distinctive:

    Leave unrelated work in the tree.

    line 27
  7. Distinctive:

    Use Conventional Commits even if the repository's earlier history differs.

    line 31
  8. Distinctive:

    Write the subject, body, and footers in English.

    line 32
  9. Very specific:

    Use <type>(<scope>): <imperative description>, or omit the scope when none fits.

    line 34
  10. Distinctive:

    Check git log --oneline -20 for the scope used in this area.

    line 36
  11. Distinctive:

    Add a body when the diff shows what changed but not why.

    line 38
  12. Very specific:

    Leave out a body that only restates the subject or lists files.

    line 39
  13. Very specific:

    Do not amend or rewrite an existing commit unless asked.

    line 45
  14. Distinctive:

    Do not push, tag, or open a pull request as part of this skill.

    line 48
  15. Distinctive:

    If the user also authorized one of those actions, follow its own workflow after committing.

    line 49

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

Turn finished work into commits that can each be reverted without breaking the build or tests. Create the commits and stop there.

Method

Read every changed file's staged and unstaged diff before deciding what belongs together. Split independent changes, but keep code and the tests that cover it in one commit.

Before staging, scan both diffs for credentials, tokens, private keys, .env contents, and internal hostnames the repository does not already publish. Unstage and withhold any affected file, then report it.

Stage one commit by path and check git status for unintended staged changes. Do not use git add -A, git add ., or git commit -a; they can sweep unrelated work into the commit.

Commit, then read git show to confirm the contents and message. Repeat until every change the task produced is committed or reported as withheld. Leave unrelated work in the tree.

Message

Use Conventional Commits even if the repository's earlier history differs. Write the subject, body, and footers in English.

Use <type>(<scope>): <imperative description>, or omit the scope when none fits. Derive type and scope from the diff, not the ticket or branch name. Check git log --oneline -20 for the scope used in this area; do not invent one when none exists.

Add a body when the diff shows what changed but not why. Leave out a body that only restates the subject or lists files. Mark a breaking change with ! or a BREAKING CHANGE: footer only when an existing caller, consumer, or configuration needs a change on its side.

Boundary

Do not amend or rewrite an existing commit unless asked; add a new one. Let hooks run. Do not pass --no-verify or -n; fix a failing hook or report it.

Do not push, tag, or open a pull request as part of this skill. If the user also authorized one of those actions, follow its own workflow after committing.

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