AGENTS.md · diff

git:20260708.f9ca59c to git:20260715.1002db3

4 added, 1 removed. Audit A to A.

# Repository Instructions

## Git Commit Message Requirements

- Subject: use English Conventional Commits without scope parentheses, such as

- `type: summary`; do not use `type(scope): summary`.

+ `type: summary`; do not use `type(scope): summary`. Write the summary in

+ plain language that product users can understand. When a change affects

+ users, describe the user-visible outcome or benefit instead of only naming

+ the internal implementation detail.

- Body: include exactly two sections, `Changed:` and `Benefit:`.

- Classification: use `chore` for repository-maintenance-only instructions,

guidance updates like this file, or non-behavioral skill maintenance.

- Skill content changes affect skill behavior and capability: inside a skill

directory, only changes limited to intentionally present `README*` files

count as documentation-only. Changes to `SKILL.md` (including its

frontmatter), references, prompts, templates, examples, scripts, or other

skill assets must use `feat` when adding capability and `fix` when correcting

behavior; do not use `docs`.

Example:

```text

chore: centralize commit message requirements

Changed:

Moved repository commit message requirements into the root AGENTS.md file.

Benefit:

Contributors have one place to check the required commit title and body format.

```

## Skill Content Rule

- Do not use the abbreviation `MDF` anywhere in a skill document (including frontmatter); always write `MarkdownFlow` in full. Exception: a skill's `description` frontmatter field may include `MarkdownFlow (MDF)` once for discoverability, so users searching for `MDF` still find the skill.