agentleFS
Sign inStart free
hanspeterdietikerhanspeterdietiker/open-agent-skills/skills/conventional-commits/SKILL.md

conventional-commits

Skill4 starsChanged 3 days agoMITView on GitHub

Use when the user asks to commit, create a commit, write a commit message, or runs /commit or /conventional-commits in any git repository - commit, commitar, mensagem de commit, conventional commits.

  • Reads credentials

58 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use github, grilling and 9 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.
  • NVIDIASkill

    github

    Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.

    Also in 3 projects that use this

  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 5 projects that use this

  • GoogleSkill

    domain-modeling

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

    Also in 4 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 5 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 5 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

  • +5 more from google

The file

Create a free account to mount
Files
SKILL.md

Conventional Commits

Cria commits no padrão Conventional Commits 1.0 em qualquer repositório.

Uso

/conventional-commits [opcional: dica de escopo ou contexto]

Fluxo

  1. Ler o estado: git status, git diff --staged, git log -n 10 --oneline.
    • Nada staged → mostre os arquivos alterados e pergunte o que entra. Nunca rode git add -A / git add . sem confirmação (evita .env, binários, lixo).
    • Mudanças sem relação entre si → proponha dividir em mais de um commit.
  2. Seguir as regras do repo, se existirem: commitlint.config.*, .commitlintrc*, .czrc, ou seção commitlint no package.json. Elas prevalecem sobre este guia (tipos, escopos, tamanho).
  3. Imitar o histórico: idioma (pt/en), estilo de escopo e uso de IDs de issue vistos no git log.
  4. Gerar a mensagem (formato abaixo).
  5. Commitar via arquivo para preservar quebras de linha em qualquer shell (bash, PowerShell, cmd):
    git commit -F <arquivo-temporario>
  6. Mostrar git log -1 --stat como confirmação.

Formato

<type>(<scope>)!: <descrição>

[corpo opcional: o porquê da mudança, linhas até 72 colunas]

[rodapés opcionais]
RegraDetalhe
Descriçãoimperativo, minúscula, sem ponto final, ≤ 72 caracteres no cabeçalho inteiro
Escopoopcional; módulo/pasta afetada (auth, api, docs). Omita se a mudança for transversal
Breaking change! após o tipo/escopo e rodapé BREAKING CHANGE: <o que quebrou>
IssueID detectado no nome da branch ou informado pelo usuário → rodapé Refs: PROJ-41 (Jira) ou Closes #41 (GitHub)

Tipos

TipoQuando
featnova funcionalidade
fixcorreção de bug
docssó documentação
styleformatação, sem mudar lógica
refactorreestruturação sem mudar comportamento
perfmelhoria de desempenho
testtestes novos ou ajustados
buildbuild, dependências
cipipelines de CI
choremanutenção que não se encaixa acima
revertreverte commit anterior

Regras fixas

  • Sem atribuição de IA: nada de Co-Authored-By: Claude, "Generated with Claude Code" ou link de sessão na mensagem.
  • Nunca --no-verify. Se um hook falhar, corrija a causa e crie um commit novo (não use --amend no commit anterior).
  • Não faça push, a menos que o usuário peça.

Exemplo

feat(auth): add password reset flow

Users had no way to recover access without contacting support.

- add forgot password form
- send verification email with expiring token
- add POST /auth/reset endpoint

Refs: PROJ-41

Créditos / Credits

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