メニュー
Conventions for authoring PRs in this repo — changesets (including attribution overrides for backfills), bump levels, summary style, PR titles. Use when creating a PR, writing or reviewing a changeset, or fixing changelog attribution.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Conventions for authoring Markdown in this repo: one sentence per line (no hard-wrapping), and ordered lists with a two-space marker so content starts at column 4. Use whenever you create OR edit ANY Markdown (.md) file — skill files, changesets, specs, docs, READMEs — no matter how small the change: even a one-line edit or a single fixed sentence counts.
Conventions for editing the dashboard's React code (dashboard/src). The Vite build runs React Compiler, so components must NOT add manual useMemo, useCallback, or React.memo. Use when editing or reviewing dashboard components, hooks, or the visx charts.
| name | pr-authoring |
| description | Conventions for authoring PRs in this repo — changesets (including attribution overrides for backfills), bump levels, summary style, PR titles. Use when creating a PR, writing or reviewing a changeset, or fixing changelog attribution. |
If a PR changes what users see or run — the CLI, collectors, indexing, the dashboard, config, the report — it must include a changeset in the same PR. Internal-only changes (tests, CI, lint setup, docs) don't get one.
Create .changeset/<kebab-slug>.md (pick a descriptive slug, not the generator's random name):
---
"repo-dive": patch
---
Imperative first sentence matching the PR title. Then paragraphs (and bullets
where they help) written for CHANGELOG readers: what changed, why, and what —
if anything — users must do. Mention when existing catalogs heal without a
re-scan, or when they don't.
Bump levels while the package is 0.x:
patch — features and fixes, which is almost everything.minor — breaking changes only (renames, catalog/config format changes users must act on).When a changeset lands in a different PR than the change it describes, the changelog would attribute it to the wrong PR/commit. @changesets/changelog-github supports overrides: put these lines at the top of the changeset body (they are parsed out and never rendered):
---
"repo-dive": patch
---
pr: #37
commit: cfc01d3239cd95ea917f4f1409d668c595c7619b
Actual summary starts here…
Use the full SHA of the squash-merge commit on main and the merged PR's number. author: @login is also supported but unused here (disableThanks is on).
main's history ("Add year shading to the lines-by-language chart"), no trailing period.changesets:version + release CI); never edit CHANGELOG.md or package.json version by hand.