Skip to content

docs(ci): title pull requests as conventional commit subjects #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aitianshi merged 1 commit into from
Nov 10, 2026
Merged

docs(ci): title pull requests as conventional commit subjects #35

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .claude/skills/file-issue/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,13 @@ repository and of the repository that owns the cause, with `gh issue list

## A pull request

The title is a conventional commit subject, because a squash merge makes it
the commit on `main`: `type(scope): summary`, lowercase except names, no
final period. Type: `feat`, `fix`, `perf`, `refactor`, `docs`, `test`, `ci`,
`build`, `chore` or `revert`. Scope: the part touched, as AGENTS.md lists them
(`standard`, `catalogue`, `runs`, `web`, `docs`, `ci`, ...). For example
`feat(catalogue): run LongMemEval on one question type`.

The body follows the template: `Closes #n` first when an issue exists, then
`## What`, `## Touches`, `## Before and after` (two images at the same width
when the change is visible; leave the section out otherwise), `## Verified`
Expand Down
10 changes: 9 additions & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -338,7 +338,15 @@ catalogue, high the backend, extreme what runs and proves), **Components**,
**Screenshot** when it is visible, **Reproduction** (the smallest steps or
input that show it), **Expected**, **Acceptance** (one checkbox per
criterion; the judge gives each its own row) and **Dependencies and
related**. A pull request's body follows `.github/pull_request_template.md`:
related**. A pull request's title is a conventional commit subject, since a
squash merge makes it the commit on `main`: `type(scope): summary`, the
summary lowercase (names keep their case) without a final period. The type is
one of `feat`, `fix`, `perf`, `refactor`, `docs`, `test`, `ci`, `build`,
`chore` or `revert`; the scope is the part it touches: `standard`,
`catalogue`, `runs`, `traces`, `compare`, `judge`, `builder`, `web`,
`execution`, `settings`, `docs`, `site`, `ci`, `release`. For example
`fix(standard): give drivers only the nullius package on PYTHONPATH`.
A pull request's body follows `.github/pull_request_template.md`:
`Closes #n`, What, Touches, Before and after (two images when the change is
visible), Verified, Risk. An assistant files either with the `/file-issue`
skill (`.claude/skills/file-issue/SKILL.md`), which produces the same shape
Expand Down
Loading