conventional-commit

Estrelas0

Forks0

Atualizado31 de maio de 2026 às 00:34

Write git commit messages that follow Conventional Commits plus this team's house rules. Use when writing or rewriting a commit message.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

cskwork

cskwork/skill-ab-eval

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

22 arquivos

SKILL.md

readonly

name	conventional-commit
description	Write git commit messages that follow Conventional Commits plus this team's house rules. Use when writing or rewriting a commit message.
license	MIT
metadata	{"owner":"example","domain":"git"}

Conventional Commit (house style)

Write every commit message exactly like this:

<type>(<scope>): <subject>

<body>

Refs: <TICKET-ID>

Rules:

Type is one of: feat, fix, docs, refactor, perf, test, chore.
Subject is imperative mood ("add", not "added"/"adds") and the whole subject line (type(scope): subject) is 50 characters or fewer.
Leave exactly one blank line between the subject and the body.
Body explains the why, wrapped at 72 columns.
Always end with a Refs: footer citing the ticket ID. If a branch name or context contains an ID like PROJ-481, use it. Never omit this footer.

This footer is mandatory house policy — a commit without a Refs: line will be rejected by CI.

Mais deste repositório

mesmo repositório

skill-ab-eval

cskwork/skill-ab-eval

Empirically measure two things for any task or domain: (1) does loading a SKILL.md actually change behavior — with_skill vs without_skill (baseline) — and (2) which CLI agent harness does the task best — claude vs codex vs gemini vs agy vs an OpenAI-compatible API. Runs the same prompt across the matrix in fresh, isolated contexts (subagents or separate CLI processes), a judge grades every output, repeated over trials, and you get a skill-lift table plus a harness leaderboard. Use to validate a new skill before shipping, catch skills that do nothing (or hurt), compare CLIs on a task you give, or pick the best harness for a domain. Triggers: evaluate skill, test skill, does my skill work, skill A/B, measure skill lift, compare CLIs, which agent is best, claude vs codex vs gemini, harness eval, benchmark agents on a task.

2026-05-310

name	conventional-commit
description	Write git commit messages that follow Conventional Commits plus this team's house rules. Use when writing or rewriting a commit message.
license	MIT
metadata	{"owner":"example","domain":"git"}

Conventional Commit (house style)

Write every commit message exactly like this:

<type>(<scope>): <subject>

<body>

Refs: <TICKET-ID>

Rules:

Type is one of: feat, fix, docs, refactor, perf, test, chore.
Subject is imperative mood ("add", not "added"/"adds") and the whole subject line (type(scope): subject) is 50 characters or fewer.
Leave exactly one blank line between the subject and the body.
Body explains the why, wrapped at 72 columns.
Always end with a Refs: footer citing the ticket ID. If a branch name or context contains an ID like PROJ-481, use it. Never omit this footer.

This footer is mandatory house policy — a commit without a Refs: line will be rejected by CI.