commit-style
01Agent
This project practices review-by-commit. A reviewer should be able to read the diff one commit at a time, in order, and follow a logical narrative — each commit a single defensible step.
Agent
This project practices review-by-commit. A reviewer should be able to read the diff one commit at a time, in order, and follow a logical narrative — each commit a single defensible step.
Agent
During implementation, the agent drops breadcrumbs — small structured decision notes — into .scratch/ /decisions.md in this repo. prepare-for-review reads them at PR time and surfaces each one either in the PR body (as a bullet under "Alternatives considered") or as an inline review comment anchored to a specific line.
Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Agent
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: