Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
22 changes: 11 additions & 11 deletions .claude/commands/address-feedback.md

Large diffs are not rendered by default.

9 changes: 4 additions & 5 deletions .claude/commands/continue-plan.md

Large diffs are not rendered by default.

4 changes: 4 additions & 0 deletions .claude/commands/handoff-plan.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,10 @@ The plan's last step writes the plan's entries, for every plan:
- `other`, with a `Release:` line: add that version's section at the top, in the style of the sections below it.
- `other`, without a `Release:` line: leave the file as it is.

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

A project can have version tags its changelog has no section for, such as the releases it made before a plan first created the changelog. They are the tags `git tag --list --merged HEAD` prints that are shaped like `v1.2.3` or `1.2.3` and match no release heading in the changelog, such as `## [1.2.3] - <date>` or `## v1.2.3`. In a project whose Landing section says `pre-release: untracked`, a tag below the first stable version never counts, because the pre-release changelog has no release section by design. The state script prints them as `changelog-backfill: <oldest>..<newest>`, as the tag alone when there is one, or as `-` when there is none, and `Update-Project.ps1` and the template's `Adopt-Project.ps1` print a request to backfill them. When there are any, and the plan isn't that backfill, list this follow-up under `## Follow-ups`, filling in `<changelog>` and `<range>`: `Backfill the changelog from past releases: add a section to <changelog> for each version tag in <range> that has none, from the tag's release notes, so the changelog covers the project's full release history.` A backfill plan writes one `## [<number>] - <date>` section for each such tag, dated with the tag's date (`git log -1 --format=%as <tag>`) and placed among the other sections by version, newest first; in a changelog of another format, it writes it in the style of the sections there. The planning session fetches each tag's release notes, with `gh release view <tag> --json body --jq .body` on GitHub or `glab release view <tag>` on GitLab, and copies the entries into the plan's steps, because the executor never calls `gh` or `glab`. For a tag without a release, it summarizes `git log --oneline <previous tag>..<tag>`, or `git log --oneline <tag>` for the first tag, into entries for the project's users. It puts each entry in one group and keeps the project's own marker for a breaking change, such as a `**Breaking:**` prefix. It adds each version's link line in order, and the `[unreleased]` link when the file has none; a changelog of another format gets no links. A backfill of many tags spreads them over several steps, a few versions each.
Expand Down
4 changes: 4 additions & 0 deletions .claude/commands/plan-bugfix.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,10 @@ The plan's last step writes the plan's entries, for every plan:
- `other`, with a `Release:` line: add that version's section at the top, in the style of the sections below it.
- `other`, without a `Release:` line: leave the file as it is.

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

A project can have version tags its changelog has no section for, such as the releases it made before a plan first created the changelog. They are the tags `git tag --list --merged HEAD` prints that are shaped like `v1.2.3` or `1.2.3` and match no release heading in the changelog, such as `## [1.2.3] - <date>` or `## v1.2.3`. In a project whose Landing section says `pre-release: untracked`, a tag below the first stable version never counts, because the pre-release changelog has no release section by design. The state script prints them as `changelog-backfill: <oldest>..<newest>`, as the tag alone when there is one, or as `-` when there is none, and `Update-Project.ps1` and the template's `Adopt-Project.ps1` print a request to backfill them. When there are any, and the plan isn't that backfill, list this follow-up under `## Follow-ups`, filling in `<changelog>` and `<range>`: `Backfill the changelog from past releases: add a section to <changelog> for each version tag in <range> that has none, from the tag's release notes, so the changelog covers the project's full release history.` A backfill plan writes one `## [<number>] - <date>` section for each such tag, dated with the tag's date (`git log -1 --format=%as <tag>`) and placed among the other sections by version, newest first; in a changelog of another format, it writes it in the style of the sections there. The planning session fetches each tag's release notes, with `gh release view <tag> --json body --jq .body` on GitHub or `glab release view <tag>` on GitLab, and copies the entries into the plan's steps, because the executor never calls `gh` or `glab`. For a tag without a release, it summarizes `git log --oneline <previous tag>..<tag>`, or `git log --oneline <tag>` for the first tag, into entries for the project's users. It puts each entry in one group and keeps the project's own marker for a breaking change, such as a `**Breaking:**` prefix. It adds each version's link line in order, and the `[unreleased]` link when the file has none; a changelog of another format gets no links. A backfill of many tags spreads them over several steps, a few versions each.
Expand Down
4 changes: 4 additions & 0 deletions .claude/commands/plan-docs.md
Original file line number Diff line number Diff line change
Expand Up @@ -111,6 +111,10 @@ The plan's last step writes the plan's entries, for every plan:
- `other`, with a `Release:` line: add that version's section at the top, in the style of the sections below it.
- `other`, without a `Release:` line: leave the file as it is.

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

A project can have version tags its changelog has no section for, such as the releases it made before a plan first created the changelog. They are the tags `git tag --list --merged HEAD` prints that are shaped like `v1.2.3` or `1.2.3` and match no release heading in the changelog, such as `## [1.2.3] - <date>` or `## v1.2.3`. In a project whose Landing section says `pre-release: untracked`, a tag below the first stable version never counts, because the pre-release changelog has no release section by design. The state script prints them as `changelog-backfill: <oldest>..<newest>`, as the tag alone when there is one, or as `-` when there is none, and `Update-Project.ps1` and the template's `Adopt-Project.ps1` print a request to backfill them. When there are any, and the plan isn't that backfill, list this follow-up under `## Follow-ups`, filling in `<changelog>` and `<range>`: `Backfill the changelog from past releases: add a section to <changelog> for each version tag in <range> that has none, from the tag's release notes, so the changelog covers the project's full release history.` A backfill plan writes one `## [<number>] - <date>` section for each such tag, dated with the tag's date (`git log -1 --format=%as <tag>`) and placed among the other sections by version, newest first; in a changelog of another format, it writes it in the style of the sections there. The planning session fetches each tag's release notes, with `gh release view <tag> --json body --jq .body` on GitHub or `glab release view <tag>` on GitLab, and copies the entries into the plan's steps, because the executor never calls `gh` or `glab`. For a tag without a release, it summarizes `git log --oneline <previous tag>..<tag>`, or `git log --oneline <tag>` for the first tag, into entries for the project's users. It puts each entry in one group and keeps the project's own marker for a breaking change, such as a `**Breaking:**` prefix. It adds each version's link line in order, and the `[unreleased]` link when the file has none; a changelog of another format gets no links. A backfill of many tags spreads them over several steps, a few versions each.
Expand Down
4 changes: 4 additions & 0 deletions .claude/commands/plan-feature.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,10 @@ The plan's last step writes the plan's entries, for every plan:
- `other`, with a `Release:` line: add that version's section at the top, in the style of the sections below it.
- `other`, without a `Release:` line: leave the file as it is.

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

A project can have version tags its changelog has no section for, such as the releases it made before a plan first created the changelog. They are the tags `git tag --list --merged HEAD` prints that are shaped like `v1.2.3` or `1.2.3` and match no release heading in the changelog, such as `## [1.2.3] - <date>` or `## v1.2.3`. In a project whose Landing section says `pre-release: untracked`, a tag below the first stable version never counts, because the pre-release changelog has no release section by design. The state script prints them as `changelog-backfill: <oldest>..<newest>`, as the tag alone when there is one, or as `-` when there is none, and `Update-Project.ps1` and the template's `Adopt-Project.ps1` print a request to backfill them. When there are any, and the plan isn't that backfill, list this follow-up under `## Follow-ups`, filling in `<changelog>` and `<range>`: `Backfill the changelog from past releases: add a section to <changelog> for each version tag in <range> that has none, from the tag's release notes, so the changelog covers the project's full release history.` A backfill plan writes one `## [<number>] - <date>` section for each such tag, dated with the tag's date (`git log -1 --format=%as <tag>`) and placed among the other sections by version, newest first; in a changelog of another format, it writes it in the style of the sections there. The planning session fetches each tag's release notes, with `gh release view <tag> --json body --jq .body` on GitHub or `glab release view <tag>` on GitLab, and copies the entries into the plan's steps, because the executor never calls `gh` or `glab`. For a tag without a release, it summarizes `git log --oneline <previous tag>..<tag>`, or `git log --oneline <tag>` for the first tag, into entries for the project's users. It puts each entry in one group and keeps the project's own marker for a breaking change, such as a `**Breaking:**` prefix. It adds each version's link line in order, and the `[unreleased]` link when the file has none; a changelog of another format gets no links. A backfill of many tags spreads them over several steps, a few versions each.
Expand Down
Loading
Loading