commit

Files (3)

• SKILL.md
• commit-footer-from-issue.sh · scripts/
• fetch-commit-guidelines.sh · scripts/

SKILL.md (first lines)

# Commit

Use this skill whenever creating or amending a commit.

## 1) Fetch and follow official commit guidelines

Run:

```bash
scripts/fetch-commit-guidelines.sh
```

Use that output as the source of truth for commit format/rules.

**Exception:** Never **manually wrap lines** or **enforce maximum line length**! Although the commit guidelines state that line length should be limited, the reasoning is not applicable to the workflows used where you are writing code. In our workflows, manually-wrapped lines make it harder to read commit messages, especially when these are converted to PR descriptions.

## 2) Write the commit body for maintainers

Commit messages are reused as PR descriptions, so optimize for skimmability:
- include brief context for why the change is needed
- include why this approach was chosen (when relevant)
- include Markdown links to relevant sources/issues/docs when useful
- be concise, human, and specific
- assume reviewers will skim the linked issue; do not restate it in depth

## 3) Generate and append commit footer lines

Run:

```bash
scripts/commit-footer-from-issue.sh <github-issue-number>
```

Or specify repo explicitly:

```bash
scripts/commit-footer-from-issue.sh <github-issue-number> owner/repo
```

Append the output at the end of the commit message.

The script always prints `Closes #<issue>`. If a Linear linkback comment exists on the GitHub issue, it also prints `Closes [ABC-123](https://linear.app/...)`.

From szokeasaurusrex/pi-agent, MIT.

More from szokeasaurusrex/pi-agent