Refactor Copilot Review Instructions and Skills

.agents/skills/README.md

@@ -2,6 +2,6 @@
 
 Canonical source for the fleet's Claude Code / opencode / Codex Skills, one directory per skill: `<name>/SKILL.md` plus optional `scripts/` and `references/`. This is the only place a skill's content is hand-authored. Everything else derived from it is generated, never hand-edited.
 
-Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
+Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. GitHub Copilot discovers repository skills under `.github/skills/`. `scripts/build_dist.py` generates both the GitHub tree and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
 
 See `AGENTS.md` for how a repo depends on these skills and `scripts/README.md` for `build_dist.py` and the installer. The procedure for creating, changing, or retiring a skill is the `skill-lifecycle` skill (`skill-lifecycle/SKILL.md` here), which this README defers to.

.agents/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.agents/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/pr-review-conduct/SKILL.md

@@ -13,9 +13,9 @@ description: >-
  full diff, or left a suppressed low-confidence finding, which opens no thread at all,
  unanswered. Also triggers when a review loop looks stuck
  (no review landing, findings that keep reappearing) or when deciding a finding is real, false,
- deferred, or a deliberate decline. Provider-specific mechanics (GitHub Copilot's request/poll/
-reply API calls) live in .github/copilot-instructions.md's "GitHub Copilot Review Runbook,"
-this skill is the contract that runbook implements, not a replacement for it.
+ deferred, or a deliberate decline. Provider-specific mechanics are implemented by
+scripts/pr_review.py and bootstrapped by .github/copilot-instructions.md. This skill is the
+ contract those surfaces implement, not a replacement for them.
 ---
 
 # PR Review Conduct
@@ -134,13 +134,11 @@ head-scoped query while still unanswered.
 - A finding is judged real but should not be fixed. That decision is never the agent's alone.
 - An architectural redesign is proposed rather than a bug fix.
 
-## Mechanics live elsewhere
+## Mechanics Live Elsewhere
 
-This skill is the provider-agnostic contract. For the actual GitHub API calls, requesting a
-Copilot review, polling for it, matching the suppressed-findings heading (its wording has moved
-more than once), verifying head-SHA and diff coverage, replying and resolving threads without a
-hand-typed id, see `.github/copilot-instructions.md` "GitHub Copilot Review Runbook" in the repo
-being worked in, and reach for `scripts/pr_review.py` (hub-hosted, invoked from a hub checkout)
-before hand-rolling any of it. `status` reports coverage, threads, suppressed findings, and shapes
-in one call, `wait` backs off in-process, and `reply` resolves a thread by matching the finding's
-own words rather than a line number a fix push can move.
+This skill is the provider-agnostic contract. Use `scripts/pr_review.py` from a hub checkout for
+the GitHub-specific API operations. `status` reports coverage, threads, body-only findings, and
+shapes in one call. `wait` requests and polls in-process. `reply` resolves a thread by matching
+the finding's own words instead of a line number a fix push can move. The repository's
+`.github/copilot-instructions.md` bootstraps Copilot into the `code-review` skill and its stable
+coverage marker. Do not reconstruct the API operations by hand.

.agents/skills/skill-lifecycle/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-lifecycle
 description: >-
- Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/ or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated plugin desyncs the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
+ Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .github/skills/ and .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/, .github/skills/, or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated distributions desync the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
 ---
 
 # Skill Lifecycle
@@ -13,7 +13,7 @@ The agent most likely to get a skill wrong is the one editing a skill, and befor
 ## The Pipeline
 
 - **`.agents/skills/<name>/SKILL.md` is the only hand-authored source**, with optional `references/` and `scripts/` directories beside it. Codex and opencode read this tree directly, project-local, and also read the global `~/.agents/skills/` copy the installer materializes.
-- **Claude Code never scans that path.** `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. The generated tree is never hand-edited, and `build_dist.py --check` exits non-zero when it was built from different source bytes than `.agents/skills/` currently holds.
+- **Generated distributions serve GitHub Copilot and Claude Code.** `scripts/build_dist.py` generates `.github/skills/` for GitHub Copilot and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. Neither generated tree is hand-edited, and `build_dist.py --check` exits non-zero when either tree differs from `.agents/skills/`.
 - **The skill set is implicit.** Every `.agents/skills/<name>/` directory carrying a `SKILL.md` is a skill, and the generated `plugin.json` derives its list from those directories, so adding or retiring a skill edits no manifest by hand. `marketplace.json` names the plugin, not the skills, and is untouched by ordinary lifecycle work.
 - **`scripts/skills_install.py`, run from a hub checkout, installs both forms per machine**: an overlay copy into `~/.agents/skills/` for Codex and opencode, marked per skill so a retired skill is removed on the next run and a foreign skill is never touched, and a user-scope plugin install for Claude Code via the `claude` CLI. Each run stamps the hub commit into `~/.agents/skills-install-stamp.json`, and `--report` reads that stamp against the checkout and exits non-zero when the machine is behind. The install is global per user, and per-repo pinning is a settled non-goal (`docs/fleet-map.md` "Skills Install Model").
 
@@ -28,13 +28,13 @@ A skill surfaces at a trigger moment. A rule that binds every action all the tim
 3. **Author the body per the `comment-and-doc-style` skill**: LF (the repo default), present tense, ASCII tiers, no semicolon in prose. Name hub paths as plain code spans rather than repo-relative links, because an installed copy resolves no repo path, and say "from a hub checkout" for anything the reader must run.
 4. **Split bulk into `references/`** when the source doc is large: the SKILL.md carries the summary and the binding rules, and each `references/*.md` carries one topic read on demand, the shape `comment-and-doc-style` uses.
 5. **Apply the doc-packaging pattern below in the same change** when the skill packages a law doc or one of its sections.
-6. **Regenerate and commit both trees together**: `python3 scripts/build_dist.py`, then commit the source and the regenerated `.claude-plugin/` in one commit. CI runs `--check` on every pull request and fails a desynced pair. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
+6. **Regenerate and commit all trees together**: `python3 scripts/build_dist.py`, then commit the source and both generated trees in one commit. CI runs `--check` on every pull request and fails a desynced distribution. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
 7. **Record the surfacing**: annotate the `AGENTS.md` "Where the Rules Live" row when the skill packages a GOVERNANCE section, or its closing paragraph when the skill is new content, so the map stays the one place coverage is read from.
 8. **Refresh the machines after merge**: re-run `python3 scripts/skills_install.py` per machine, the cadence `docs/host-setup.md` "Fleet Skills Install" states. Until then every machine serves the previous skill set, which `--report` says.
 
 ## Changing or Retiring a Skill
 
-- **Edit only the source tree.** Any content change under `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
+- **Edit only the source tree.** Any skill-content change under `.github/skills/` or `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
 - **Retiring is deleting the source directory and regenerating.** The derived `plugin.json` list shrinks with it, and the installer's per-skill markers remove the retired skill from `~/.agents/skills/` on each machine's next run.
 - **A deletion sweeps the prose that references the skill**, in the same change rather than as follow-up: the `AGENTS.md` map row or paragraph naming it, any law-doc packaging pointer to it, and any sibling skill that disambiguates against it. A law-doc section that had moved its full rules into the skill takes them back, or is retired with it, so no rule is silently lost with the skill that carried it.
 - **Renaming is a retire plus a create** as far as the installer's markers and the plugin list are concerned, so sweep references the same way.

.claude-plugin/fleet-skills/.claude-plugin/plugin.json

@@ -9,6 +9,7 @@
  "./skills/agent-conduct",
  "./skills/audit-a-repo",
  "./skills/carried-instruction-file-guard",
+ "./skills/code-review",
  "./skills/comment-and-doc-style",
  "./skills/copilot-instructions-keeper",
  "./skills/dotnet-codestyle",

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-2796eec540f960cb
+cf555123c5d2982d

.claude-plugin/fleet-skills/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.claude-plugin/fleet-skills/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/README.md

@@ -2,6 +2,6 @@
 
 Canonical source for the fleet's Claude Code / opencode / Codex Skills, one directory per skill: `<name>/SKILL.md` plus optional `scripts/` and `references/`. This is the only place a skill's content is hand-authored. Everything else derived from it is generated, never hand-edited.
 
-Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
+Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. GitHub Copilot discovers repository skills under `.github/skills/`. `scripts/build_dist.py` generates both the GitHub tree and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
 
 See `AGENTS.md` for how a repo depends on these skills and `scripts/README.md` for `build_dist.py` and the installer. The procedure for creating, changing, or retiring a skill is the `skill-lifecycle` skill (`skill-lifecycle/SKILL.md` here), which this README defers to.

.agents/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.agents/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/pr-review-conduct/SKILL.md

@@ -13,9 +13,9 @@ description: >-
  full diff, or left a suppressed low-confidence finding, which opens no thread at all,
  unanswered. Also triggers when a review loop looks stuck
  (no review landing, findings that keep reappearing) or when deciding a finding is real, false,
- deferred, or a deliberate decline. Provider-specific mechanics (GitHub Copilot's request/poll/
-reply API calls) live in .github/copilot-instructions.md's "GitHub Copilot Review Runbook,"
-this skill is the contract that runbook implements, not a replacement for it.
+ deferred, or a deliberate decline. Provider-specific mechanics are implemented by
+scripts/pr_review.py and bootstrapped by .github/copilot-instructions.md. This skill is the
+ contract those surfaces implement, not a replacement for them.
 ---
 
 # PR Review Conduct
@@ -134,13 +134,11 @@ head-scoped query while still unanswered.
 - A finding is judged real but should not be fixed. That decision is never the agent's alone.
 - An architectural redesign is proposed rather than a bug fix.
 
-## Mechanics live elsewhere
+## Mechanics Live Elsewhere
 
-This skill is the provider-agnostic contract. For the actual GitHub API calls, requesting a
-Copilot review, polling for it, matching the suppressed-findings heading (its wording has moved
-more than once), verifying head-SHA and diff coverage, replying and resolving threads without a
-hand-typed id, see `.github/copilot-instructions.md` "GitHub Copilot Review Runbook" in the repo
-being worked in, and reach for `scripts/pr_review.py` (hub-hosted, invoked from a hub checkout)
-before hand-rolling any of it. `status` reports coverage, threads, suppressed findings, and shapes
-in one call, `wait` backs off in-process, and `reply` resolves a thread by matching the finding's
-own words rather than a line number a fix push can move.
+This skill is the provider-agnostic contract. Use `scripts/pr_review.py` from a hub checkout for
+the GitHub-specific API operations. `status` reports coverage, threads, body-only findings, and
+shapes in one call. `wait` requests and polls in-process. `reply` resolves a thread by matching
+the finding's own words instead of a line number a fix push can move. The repository's
+`.github/copilot-instructions.md` bootstraps Copilot into the `code-review` skill and its stable
+coverage marker. Do not reconstruct the API operations by hand.

.agents/skills/skill-lifecycle/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-lifecycle
 description: >-
- Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/ or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated plugin desyncs the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
+ Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .github/skills/ and .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/, .github/skills/, or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated distributions desync the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
 ---
 
 # Skill Lifecycle
@@ -13,7 +13,7 @@ The agent most likely to get a skill wrong is the one editing a skill, and befor
 ## The Pipeline
 
 - **`.agents/skills/<name>/SKILL.md` is the only hand-authored source**, with optional `references/` and `scripts/` directories beside it. Codex and opencode read this tree directly, project-local, and also read the global `~/.agents/skills/` copy the installer materializes.
-- **Claude Code never scans that path.** `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. The generated tree is never hand-edited, and `build_dist.py --check` exits non-zero when it was built from different source bytes than `.agents/skills/` currently holds.
+- **Generated distributions serve GitHub Copilot and Claude Code.** `scripts/build_dist.py` generates `.github/skills/` for GitHub Copilot and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. Neither generated tree is hand-edited, and `build_dist.py --check` exits non-zero when either tree differs from `.agents/skills/`.
 - **The skill set is implicit.** Every `.agents/skills/<name>/` directory carrying a `SKILL.md` is a skill, and the generated `plugin.json` derives its list from those directories, so adding or retiring a skill edits no manifest by hand. `marketplace.json` names the plugin, not the skills, and is untouched by ordinary lifecycle work.
 - **`scripts/skills_install.py`, run from a hub checkout, installs both forms per machine**: an overlay copy into `~/.agents/skills/` for Codex and opencode, marked per skill so a retired skill is removed on the next run and a foreign skill is never touched, and a user-scope plugin install for Claude Code via the `claude` CLI. Each run stamps the hub commit into `~/.agents/skills-install-stamp.json`, and `--report` reads that stamp against the checkout and exits non-zero when the machine is behind. The install is global per user, and per-repo pinning is a settled non-goal (`docs/fleet-map.md` "Skills Install Model").
 
@@ -28,13 +28,13 @@ A skill surfaces at a trigger moment. A rule that binds every action all the tim
 3. **Author the body per the `comment-and-doc-style` skill**: LF (the repo default), present tense, ASCII tiers, no semicolon in prose. Name hub paths as plain code spans rather than repo-relative links, because an installed copy resolves no repo path, and say "from a hub checkout" for anything the reader must run.
 4. **Split bulk into `references/`** when the source doc is large: the SKILL.md carries the summary and the binding rules, and each `references/*.md` carries one topic read on demand, the shape `comment-and-doc-style` uses.
 5. **Apply the doc-packaging pattern below in the same change** when the skill packages a law doc or one of its sections.
-6. **Regenerate and commit both trees together**: `python3 scripts/build_dist.py`, then commit the source and the regenerated `.claude-plugin/` in one commit. CI runs `--check` on every pull request and fails a desynced pair. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
+6. **Regenerate and commit all trees together**: `python3 scripts/build_dist.py`, then commit the source and both generated trees in one commit. CI runs `--check` on every pull request and fails a desynced distribution. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
 7. **Record the surfacing**: annotate the `AGENTS.md` "Where the Rules Live" row when the skill packages a GOVERNANCE section, or its closing paragraph when the skill is new content, so the map stays the one place coverage is read from.
 8. **Refresh the machines after merge**: re-run `python3 scripts/skills_install.py` per machine, the cadence `docs/host-setup.md` "Fleet Skills Install" states. Until then every machine serves the previous skill set, which `--report` says.
 
 ## Changing or Retiring a Skill
 
-- **Edit only the source tree.** Any content change under `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
+- **Edit only the source tree.** Any skill-content change under `.github/skills/` or `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
 - **Retiring is deleting the source directory and regenerating.** The derived `plugin.json` list shrinks with it, and the installer's per-skill markers remove the retired skill from `~/.agents/skills/` on each machine's next run.
 - **A deletion sweeps the prose that references the skill**, in the same change rather than as follow-up: the `AGENTS.md` map row or paragraph naming it, any law-doc packaging pointer to it, and any sibling skill that disambiguates against it. A law-doc section that had moved its full rules into the skill takes them back, or is retired with it, so no rule is silently lost with the skill that carried it.
 - **Renaming is a retire plus a create** as far as the installer's markers and the plugin list are concerned, so sweep references the same way.

.claude-plugin/fleet-skills/.claude-plugin/plugin.json

@@ -9,6 +9,7 @@
  "./skills/agent-conduct",
  "./skills/audit-a-repo",
  "./skills/carried-instruction-file-guard",
+ "./skills/code-review",
  "./skills/comment-and-doc-style",
  "./skills/copilot-instructions-keeper",
  "./skills/dotnet-codestyle",

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-2796eec540f960cb
+cf555123c5d2982d

.claude-plugin/fleet-skills/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.claude-plugin/fleet-skills/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/README.md

@@ -2,6 +2,6 @@
 
 Canonical source for the fleet's Claude Code / opencode / Codex Skills, one directory per skill: `<name>/SKILL.md` plus optional `scripts/` and `references/`. This is the only place a skill's content is hand-authored. Everything else derived from it is generated, never hand-edited.
 
-Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
+Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. GitHub Copilot discovers repository skills under `.github/skills/`. `scripts/build_dist.py` generates both the GitHub tree and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
 
 See `AGENTS.md` for how a repo depends on these skills and `scripts/README.md` for `build_dist.py` and the installer. The procedure for creating, changing, or retiring a skill is the `skill-lifecycle` skill (`skill-lifecycle/SKILL.md` here), which this README defers to.

.agents/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.agents/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/pr-review-conduct/SKILL.md

@@ -13,9 +13,9 @@ description: >-
  full diff, or left a suppressed low-confidence finding, which opens no thread at all,
  unanswered. Also triggers when a review loop looks stuck
  (no review landing, findings that keep reappearing) or when deciding a finding is real, false,
- deferred, or a deliberate decline. Provider-specific mechanics (GitHub Copilot's request/poll/
-reply API calls) live in .github/copilot-instructions.md's "GitHub Copilot Review Runbook,"
-this skill is the contract that runbook implements, not a replacement for it.
+ deferred, or a deliberate decline. Provider-specific mechanics are implemented by
+scripts/pr_review.py and bootstrapped by .github/copilot-instructions.md. This skill is the
+ contract those surfaces implement, not a replacement for them.
 ---
 
 # PR Review Conduct
@@ -134,13 +134,11 @@ head-scoped query while still unanswered.
 - A finding is judged real but should not be fixed. That decision is never the agent's alone.
 - An architectural redesign is proposed rather than a bug fix.
 
-## Mechanics live elsewhere
+## Mechanics Live Elsewhere
 
-This skill is the provider-agnostic contract. For the actual GitHub API calls, requesting a
-Copilot review, polling for it, matching the suppressed-findings heading (its wording has moved
-more than once), verifying head-SHA and diff coverage, replying and resolving threads without a
-hand-typed id, see `.github/copilot-instructions.md` "GitHub Copilot Review Runbook" in the repo
-being worked in, and reach for `scripts/pr_review.py` (hub-hosted, invoked from a hub checkout)
-before hand-rolling any of it. `status` reports coverage, threads, suppressed findings, and shapes
-in one call, `wait` backs off in-process, and `reply` resolves a thread by matching the finding's
-own words rather than a line number a fix push can move.
+This skill is the provider-agnostic contract. Use `scripts/pr_review.py` from a hub checkout for
+the GitHub-specific API operations. `status` reports coverage, threads, body-only findings, and
+shapes in one call. `wait` requests and polls in-process. `reply` resolves a thread by matching
+the finding's own words instead of a line number a fix push can move. The repository's
+`.github/copilot-instructions.md` bootstraps Copilot into the `code-review` skill and its stable
+coverage marker. Do not reconstruct the API operations by hand.

.agents/skills/skill-lifecycle/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-lifecycle
 description: >-
- Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/ or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated plugin desyncs the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
+ Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .github/skills/ and .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/, .github/skills/, or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated distributions desync the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
 ---
 
 # Skill Lifecycle
@@ -13,7 +13,7 @@ The agent most likely to get a skill wrong is the one editing a skill, and befor
 ## The Pipeline
 
 - **`.agents/skills/<name>/SKILL.md` is the only hand-authored source**, with optional `references/` and `scripts/` directories beside it. Codex and opencode read this tree directly, project-local, and also read the global `~/.agents/skills/` copy the installer materializes.
-- **Claude Code never scans that path.** `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. The generated tree is never hand-edited, and `build_dist.py --check` exits non-zero when it was built from different source bytes than `.agents/skills/` currently holds.
+- **Generated distributions serve GitHub Copilot and Claude Code.** `scripts/build_dist.py` generates `.github/skills/` for GitHub Copilot and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. Neither generated tree is hand-edited, and `build_dist.py --check` exits non-zero when either tree differs from `.agents/skills/`.
 - **The skill set is implicit.** Every `.agents/skills/<name>/` directory carrying a `SKILL.md` is a skill, and the generated `plugin.json` derives its list from those directories, so adding or retiring a skill edits no manifest by hand. `marketplace.json` names the plugin, not the skills, and is untouched by ordinary lifecycle work.
 - **`scripts/skills_install.py`, run from a hub checkout, installs both forms per machine**: an overlay copy into `~/.agents/skills/` for Codex and opencode, marked per skill so a retired skill is removed on the next run and a foreign skill is never touched, and a user-scope plugin install for Claude Code via the `claude` CLI. Each run stamps the hub commit into `~/.agents/skills-install-stamp.json`, and `--report` reads that stamp against the checkout and exits non-zero when the machine is behind. The install is global per user, and per-repo pinning is a settled non-goal (`docs/fleet-map.md` "Skills Install Model").
 
@@ -28,13 +28,13 @@ A skill surfaces at a trigger moment. A rule that binds every action all the tim
 3. **Author the body per the `comment-and-doc-style` skill**: LF (the repo default), present tense, ASCII tiers, no semicolon in prose. Name hub paths as plain code spans rather than repo-relative links, because an installed copy resolves no repo path, and say "from a hub checkout" for anything the reader must run.
 4. **Split bulk into `references/`** when the source doc is large: the SKILL.md carries the summary and the binding rules, and each `references/*.md` carries one topic read on demand, the shape `comment-and-doc-style` uses.
 5. **Apply the doc-packaging pattern below in the same change** when the skill packages a law doc or one of its sections.
-6. **Regenerate and commit both trees together**: `python3 scripts/build_dist.py`, then commit the source and the regenerated `.claude-plugin/` in one commit. CI runs `--check` on every pull request and fails a desynced pair. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
+6. **Regenerate and commit all trees together**: `python3 scripts/build_dist.py`, then commit the source and both generated trees in one commit. CI runs `--check` on every pull request and fails a desynced distribution. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
 7. **Record the surfacing**: annotate the `AGENTS.md` "Where the Rules Live" row when the skill packages a GOVERNANCE section, or its closing paragraph when the skill is new content, so the map stays the one place coverage is read from.
 8. **Refresh the machines after merge**: re-run `python3 scripts/skills_install.py` per machine, the cadence `docs/host-setup.md` "Fleet Skills Install" states. Until then every machine serves the previous skill set, which `--report` says.
 
 ## Changing or Retiring a Skill
 
-- **Edit only the source tree.** Any content change under `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
+- **Edit only the source tree.** Any skill-content change under `.github/skills/` or `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
 - **Retiring is deleting the source directory and regenerating.** The derived `plugin.json` list shrinks with it, and the installer's per-skill markers remove the retired skill from `~/.agents/skills/` on each machine's next run.
 - **A deletion sweeps the prose that references the skill**, in the same change rather than as follow-up: the `AGENTS.md` map row or paragraph naming it, any law-doc packaging pointer to it, and any sibling skill that disambiguates against it. A law-doc section that had moved its full rules into the skill takes them back, or is retired with it, so no rule is silently lost with the skill that carried it.
 - **Renaming is a retire plus a create** as far as the installer's markers and the plugin list are concerned, so sweep references the same way.

.claude-plugin/fleet-skills/.claude-plugin/plugin.json

@@ -9,6 +9,7 @@
  "./skills/agent-conduct",
  "./skills/audit-a-repo",
  "./skills/carried-instruction-file-guard",
+ "./skills/code-review",
  "./skills/comment-and-doc-style",
  "./skills/copilot-instructions-keeper",
  "./skills/dotnet-codestyle",

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-2796eec540f960cb
+cf555123c5d2982d

.claude-plugin/fleet-skills/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.claude-plugin/fleet-skills/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/README.md

@@ -2,6 +2,6 @@
 
 Canonical source for the fleet's Claude Code / opencode / Codex Skills, one directory per skill: `<name>/SKILL.md` plus optional `scripts/` and `references/`. This is the only place a skill's content is hand-authored. Everything else derived from it is generated, never hand-edited.
 
-Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
+Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. GitHub Copilot discovers repository skills under `.github/skills/`. `scripts/build_dist.py` generates both the GitHub tree and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
 
 See `AGENTS.md` for how a repo depends on these skills and `scripts/README.md` for `build_dist.py` and the installer. The procedure for creating, changing, or retiring a skill is the `skill-lifecycle` skill (`skill-lifecycle/SKILL.md` here), which this README defers to.

.agents/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.agents/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/pr-review-conduct/SKILL.md

@@ -13,9 +13,9 @@ description: >-
  full diff, or left a suppressed low-confidence finding, which opens no thread at all,
  unanswered. Also triggers when a review loop looks stuck
  (no review landing, findings that keep reappearing) or when deciding a finding is real, false,
- deferred, or a deliberate decline. Provider-specific mechanics (GitHub Copilot's request/poll/
-reply API calls) live in .github/copilot-instructions.md's "GitHub Copilot Review Runbook,"
-this skill is the contract that runbook implements, not a replacement for it.
+ deferred, or a deliberate decline. Provider-specific mechanics are implemented by
+scripts/pr_review.py and bootstrapped by .github/copilot-instructions.md. This skill is the
+ contract those surfaces implement, not a replacement for them.
 ---
 
 # PR Review Conduct
@@ -134,13 +134,11 @@ head-scoped query while still unanswered.
 - A finding is judged real but should not be fixed. That decision is never the agent's alone.
 - An architectural redesign is proposed rather than a bug fix.
 
-## Mechanics live elsewhere
+## Mechanics Live Elsewhere
 
-This skill is the provider-agnostic contract. For the actual GitHub API calls, requesting a
-Copilot review, polling for it, matching the suppressed-findings heading (its wording has moved
-more than once), verifying head-SHA and diff coverage, replying and resolving threads without a
-hand-typed id, see `.github/copilot-instructions.md` "GitHub Copilot Review Runbook" in the repo
-being worked in, and reach for `scripts/pr_review.py` (hub-hosted, invoked from a hub checkout)
-before hand-rolling any of it. `status` reports coverage, threads, suppressed findings, and shapes
-in one call, `wait` backs off in-process, and `reply` resolves a thread by matching the finding's
-own words rather than a line number a fix push can move.
+This skill is the provider-agnostic contract. Use `scripts/pr_review.py` from a hub checkout for
+the GitHub-specific API operations. `status` reports coverage, threads, body-only findings, and
+shapes in one call. `wait` requests and polls in-process. `reply` resolves a thread by matching
+the finding's own words instead of a line number a fix push can move. The repository's
+`.github/copilot-instructions.md` bootstraps Copilot into the `code-review` skill and its stable
+coverage marker. Do not reconstruct the API operations by hand.

.agents/skills/skill-lifecycle/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-lifecycle
 description: >-
- Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/ or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated plugin desyncs the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
+ Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .github/skills/ and .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/, .github/skills/, or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated distributions desync the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
 ---
 
 # Skill Lifecycle
@@ -13,7 +13,7 @@ The agent most likely to get a skill wrong is the one editing a skill, and befor
 ## The Pipeline
 
 - **`.agents/skills/<name>/SKILL.md` is the only hand-authored source**, with optional `references/` and `scripts/` directories beside it. Codex and opencode read this tree directly, project-local, and also read the global `~/.agents/skills/` copy the installer materializes.
-- **Claude Code never scans that path.** `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. The generated tree is never hand-edited, and `build_dist.py --check` exits non-zero when it was built from different source bytes than `.agents/skills/` currently holds.
+- **Generated distributions serve GitHub Copilot and Claude Code.** `scripts/build_dist.py` generates `.github/skills/` for GitHub Copilot and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. Neither generated tree is hand-edited, and `build_dist.py --check` exits non-zero when either tree differs from `.agents/skills/`.
 - **The skill set is implicit.** Every `.agents/skills/<name>/` directory carrying a `SKILL.md` is a skill, and the generated `plugin.json` derives its list from those directories, so adding or retiring a skill edits no manifest by hand. `marketplace.json` names the plugin, not the skills, and is untouched by ordinary lifecycle work.
 - **`scripts/skills_install.py`, run from a hub checkout, installs both forms per machine**: an overlay copy into `~/.agents/skills/` for Codex and opencode, marked per skill so a retired skill is removed on the next run and a foreign skill is never touched, and a user-scope plugin install for Claude Code via the `claude` CLI. Each run stamps the hub commit into `~/.agents/skills-install-stamp.json`, and `--report` reads that stamp against the checkout and exits non-zero when the machine is behind. The install is global per user, and per-repo pinning is a settled non-goal (`docs/fleet-map.md` "Skills Install Model").
 
@@ -28,13 +28,13 @@ A skill surfaces at a trigger moment. A rule that binds every action all the tim
 3. **Author the body per the `comment-and-doc-style` skill**: LF (the repo default), present tense, ASCII tiers, no semicolon in prose. Name hub paths as plain code spans rather than repo-relative links, because an installed copy resolves no repo path, and say "from a hub checkout" for anything the reader must run.
 4. **Split bulk into `references/`** when the source doc is large: the SKILL.md carries the summary and the binding rules, and each `references/*.md` carries one topic read on demand, the shape `comment-and-doc-style` uses.
 5. **Apply the doc-packaging pattern below in the same change** when the skill packages a law doc or one of its sections.
-6. **Regenerate and commit both trees together**: `python3 scripts/build_dist.py`, then commit the source and the regenerated `.claude-plugin/` in one commit. CI runs `--check` on every pull request and fails a desynced pair. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
+6. **Regenerate and commit all trees together**: `python3 scripts/build_dist.py`, then commit the source and both generated trees in one commit. CI runs `--check` on every pull request and fails a desynced distribution. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
 7. **Record the surfacing**: annotate the `AGENTS.md` "Where the Rules Live" row when the skill packages a GOVERNANCE section, or its closing paragraph when the skill is new content, so the map stays the one place coverage is read from.
 8. **Refresh the machines after merge**: re-run `python3 scripts/skills_install.py` per machine, the cadence `docs/host-setup.md` "Fleet Skills Install" states. Until then every machine serves the previous skill set, which `--report` says.
 
 ## Changing or Retiring a Skill
 
-- **Edit only the source tree.** Any content change under `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
+- **Edit only the source tree.** Any skill-content change under `.github/skills/` or `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
 - **Retiring is deleting the source directory and regenerating.** The derived `plugin.json` list shrinks with it, and the installer's per-skill markers remove the retired skill from `~/.agents/skills/` on each machine's next run.
 - **A deletion sweeps the prose that references the skill**, in the same change rather than as follow-up: the `AGENTS.md` map row or paragraph naming it, any law-doc packaging pointer to it, and any sibling skill that disambiguates against it. A law-doc section that had moved its full rules into the skill takes them back, or is retired with it, so no rule is silently lost with the skill that carried it.
 - **Renaming is a retire plus a create** as far as the installer's markers and the plugin list are concerned, so sweep references the same way.

.claude-plugin/fleet-skills/.claude-plugin/plugin.json

@@ -9,6 +9,7 @@
  "./skills/agent-conduct",
  "./skills/audit-a-repo",
  "./skills/carried-instruction-file-guard",
+ "./skills/code-review",
  "./skills/comment-and-doc-style",
  "./skills/copilot-instructions-keeper",
  "./skills/dotnet-codestyle",

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-2796eec540f960cb
+cf555123c5d2982d

.claude-plugin/fleet-skills/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.claude-plugin/fleet-skills/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/README.md

@@ -2,6 +2,6 @@
 
 Canonical source for the fleet's Claude Code / opencode / Codex Skills, one directory per skill: `<name>/SKILL.md` plus optional `scripts/` and `references/`. This is the only place a skill's content is hand-authored. Everything else derived from it is generated, never hand-edited.
 
-Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
+Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. GitHub Copilot discovers repository skills under `.github/skills/`. `scripts/build_dist.py` generates both the GitHub tree and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
 
 See `AGENTS.md` for how a repo depends on these skills and `scripts/README.md` for `build_dist.py` and the installer. The procedure for creating, changing, or retiring a skill is the `skill-lifecycle` skill (`skill-lifecycle/SKILL.md` here), which this README defers to.

.agents/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.agents/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/pr-review-conduct/SKILL.md

@@ -13,9 +13,9 @@ description: >-
  full diff, or left a suppressed low-confidence finding, which opens no thread at all,
  unanswered. Also triggers when a review loop looks stuck
  (no review landing, findings that keep reappearing) or when deciding a finding is real, false,
- deferred, or a deliberate decline. Provider-specific mechanics (GitHub Copilot's request/poll/
-reply API calls) live in .github/copilot-instructions.md's "GitHub Copilot Review Runbook,"
-this skill is the contract that runbook implements, not a replacement for it.
+ deferred, or a deliberate decline. Provider-specific mechanics are implemented by
+scripts/pr_review.py and bootstrapped by .github/copilot-instructions.md. This skill is the
+ contract those surfaces implement, not a replacement for them.
 ---
 
 # PR Review Conduct
@@ -134,13 +134,11 @@ head-scoped query while still unanswered.
 - A finding is judged real but should not be fixed. That decision is never the agent's alone.
 - An architectural redesign is proposed rather than a bug fix.
 
-## Mechanics live elsewhere
+## Mechanics Live Elsewhere
 
-This skill is the provider-agnostic contract. For the actual GitHub API calls, requesting a
-Copilot review, polling for it, matching the suppressed-findings heading (its wording has moved
-more than once), verifying head-SHA and diff coverage, replying and resolving threads without a
-hand-typed id, see `.github/copilot-instructions.md` "GitHub Copilot Review Runbook" in the repo
-being worked in, and reach for `scripts/pr_review.py` (hub-hosted, invoked from a hub checkout)
-before hand-rolling any of it. `status` reports coverage, threads, suppressed findings, and shapes
-in one call, `wait` backs off in-process, and `reply` resolves a thread by matching the finding's
-own words rather than a line number a fix push can move.
+This skill is the provider-agnostic contract. Use `scripts/pr_review.py` from a hub checkout for
+the GitHub-specific API operations. `status` reports coverage, threads, body-only findings, and
+shapes in one call. `wait` requests and polls in-process. `reply` resolves a thread by matching
+the finding's own words instead of a line number a fix push can move. The repository's
+`.github/copilot-instructions.md` bootstraps Copilot into the `code-review` skill and its stable
+coverage marker. Do not reconstruct the API operations by hand.

.agents/skills/skill-lifecycle/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-lifecycle
 description: >-
- Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/ or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated plugin desyncs the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
+ Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .github/skills/ and .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/, .github/skills/, or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated distributions desync the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
 ---
 
 # Skill Lifecycle
@@ -13,7 +13,7 @@ The agent most likely to get a skill wrong is the one editing a skill, and befor
 ## The Pipeline
 
 - **`.agents/skills/<name>/SKILL.md` is the only hand-authored source**, with optional `references/` and `scripts/` directories beside it. Codex and opencode read this tree directly, project-local, and also read the global `~/.agents/skills/` copy the installer materializes.
-- **Claude Code never scans that path.** `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. The generated tree is never hand-edited, and `build_dist.py --check` exits non-zero when it was built from different source bytes than `.agents/skills/` currently holds.
+- **Generated distributions serve GitHub Copilot and Claude Code.** `scripts/build_dist.py` generates `.github/skills/` for GitHub Copilot and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. Neither generated tree is hand-edited, and `build_dist.py --check` exits non-zero when either tree differs from `.agents/skills/`.
 - **The skill set is implicit.** Every `.agents/skills/<name>/` directory carrying a `SKILL.md` is a skill, and the generated `plugin.json` derives its list from those directories, so adding or retiring a skill edits no manifest by hand. `marketplace.json` names the plugin, not the skills, and is untouched by ordinary lifecycle work.
 - **`scripts/skills_install.py`, run from a hub checkout, installs both forms per machine**: an overlay copy into `~/.agents/skills/` for Codex and opencode, marked per skill so a retired skill is removed on the next run and a foreign skill is never touched, and a user-scope plugin install for Claude Code via the `claude` CLI. Each run stamps the hub commit into `~/.agents/skills-install-stamp.json`, and `--report` reads that stamp against the checkout and exits non-zero when the machine is behind. The install is global per user, and per-repo pinning is a settled non-goal (`docs/fleet-map.md` "Skills Install Model").
 
@@ -28,13 +28,13 @@ A skill surfaces at a trigger moment. A rule that binds every action all the tim
 3. **Author the body per the `comment-and-doc-style` skill**: LF (the repo default), present tense, ASCII tiers, no semicolon in prose. Name hub paths as plain code spans rather than repo-relative links, because an installed copy resolves no repo path, and say "from a hub checkout" for anything the reader must run.
 4. **Split bulk into `references/`** when the source doc is large: the SKILL.md carries the summary and the binding rules, and each `references/*.md` carries one topic read on demand, the shape `comment-and-doc-style` uses.
 5. **Apply the doc-packaging pattern below in the same change** when the skill packages a law doc or one of its sections.
-6. **Regenerate and commit both trees together**: `python3 scripts/build_dist.py`, then commit the source and the regenerated `.claude-plugin/` in one commit. CI runs `--check` on every pull request and fails a desynced pair. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
+6. **Regenerate and commit all trees together**: `python3 scripts/build_dist.py`, then commit the source and both generated trees in one commit. CI runs `--check` on every pull request and fails a desynced distribution. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
 7. **Record the surfacing**: annotate the `AGENTS.md` "Where the Rules Live" row when the skill packages a GOVERNANCE section, or its closing paragraph when the skill is new content, so the map stays the one place coverage is read from.
 8. **Refresh the machines after merge**: re-run `python3 scripts/skills_install.py` per machine, the cadence `docs/host-setup.md` "Fleet Skills Install" states. Until then every machine serves the previous skill set, which `--report` says.
 
 ## Changing or Retiring a Skill
 
-- **Edit only the source tree.** Any content change under `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
+- **Edit only the source tree.** Any skill-content change under `.github/skills/` or `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
 - **Retiring is deleting the source directory and regenerating.** The derived `plugin.json` list shrinks with it, and the installer's per-skill markers remove the retired skill from `~/.agents/skills/` on each machine's next run.
 - **A deletion sweeps the prose that references the skill**, in the same change rather than as follow-up: the `AGENTS.md` map row or paragraph naming it, any law-doc packaging pointer to it, and any sibling skill that disambiguates against it. A law-doc section that had moved its full rules into the skill takes them back, or is retired with it, so no rule is silently lost with the skill that carried it.
 - **Renaming is a retire plus a create** as far as the installer's markers and the plugin list are concerned, so sweep references the same way.

.claude-plugin/fleet-skills/.claude-plugin/plugin.json

@@ -9,6 +9,7 @@
  "./skills/agent-conduct",
  "./skills/audit-a-repo",
  "./skills/carried-instruction-file-guard",
+ "./skills/code-review",
  "./skills/comment-and-doc-style",
  "./skills/copilot-instructions-keeper",
  "./skills/dotnet-codestyle",

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-2796eec540f960cb
+cf555123c5d2982d

.claude-plugin/fleet-skills/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.claude-plugin/fleet-skills/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/README.md

@@ -2,6 +2,6 @@
 
 Canonical source for the fleet's Claude Code / opencode / Codex Skills, one directory per skill: `<name>/SKILL.md` plus optional `scripts/` and `references/`. This is the only place a skill's content is hand-authored. Everything else derived from it is generated, never hand-edited.
 
-Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
+Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. GitHub Copilot discovers repository skills under `.github/skills/`. `scripts/build_dist.py` generates both the GitHub tree and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
 
 See `AGENTS.md` for how a repo depends on these skills and `scripts/README.md` for `build_dist.py` and the installer. The procedure for creating, changing, or retiring a skill is the `skill-lifecycle` skill (`skill-lifecycle/SKILL.md` here), which this README defers to.

.agents/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.agents/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/pr-review-conduct/SKILL.md

@@ -13,9 +13,9 @@ description: >-
  full diff, or left a suppressed low-confidence finding, which opens no thread at all,
  unanswered. Also triggers when a review loop looks stuck
  (no review landing, findings that keep reappearing) or when deciding a finding is real, false,
- deferred, or a deliberate decline. Provider-specific mechanics (GitHub Copilot's request/poll/
-reply API calls) live in .github/copilot-instructions.md's "GitHub Copilot Review Runbook,"
-this skill is the contract that runbook implements, not a replacement for it.
+ deferred, or a deliberate decline. Provider-specific mechanics are implemented by
+scripts/pr_review.py and bootstrapped by .github/copilot-instructions.md. This skill is the
+ contract those surfaces implement, not a replacement for them.
 ---
 
 # PR Review Conduct
@@ -134,13 +134,11 @@ head-scoped query while still unanswered.
 - A finding is judged real but should not be fixed. That decision is never the agent's alone.
 - An architectural redesign is proposed rather than a bug fix.
 
-## Mechanics live elsewhere
+## Mechanics Live Elsewhere
 
-This skill is the provider-agnostic contract. For the actual GitHub API calls, requesting a
-Copilot review, polling for it, matching the suppressed-findings heading (its wording has moved
-more than once), verifying head-SHA and diff coverage, replying and resolving threads without a
-hand-typed id, see `.github/copilot-instructions.md` "GitHub Copilot Review Runbook" in the repo
-being worked in, and reach for `scripts/pr_review.py` (hub-hosted, invoked from a hub checkout)
-before hand-rolling any of it. `status` reports coverage, threads, suppressed findings, and shapes
-in one call, `wait` backs off in-process, and `reply` resolves a thread by matching the finding's
-own words rather than a line number a fix push can move.
+This skill is the provider-agnostic contract. Use `scripts/pr_review.py` from a hub checkout for
+the GitHub-specific API operations. `status` reports coverage, threads, body-only findings, and
+shapes in one call. `wait` requests and polls in-process. `reply` resolves a thread by matching
+the finding's own words instead of a line number a fix push can move. The repository's
+`.github/copilot-instructions.md` bootstraps Copilot into the `code-review` skill and its stable
+coverage marker. Do not reconstruct the API operations by hand.

.agents/skills/skill-lifecycle/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-lifecycle
 description: >-
- Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/ or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated plugin desyncs the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
+ Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .github/skills/ and .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/, .github/skills/, or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated distributions desync the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
 ---
 
 # Skill Lifecycle
@@ -13,7 +13,7 @@ The agent most likely to get a skill wrong is the one editing a skill, and befor
 ## The Pipeline
 
 - **`.agents/skills/<name>/SKILL.md` is the only hand-authored source**, with optional `references/` and `scripts/` directories beside it. Codex and opencode read this tree directly, project-local, and also read the global `~/.agents/skills/` copy the installer materializes.
-- **Claude Code never scans that path.** `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. The generated tree is never hand-edited, and `build_dist.py --check` exits non-zero when it was built from different source bytes than `.agents/skills/` currently holds.
+- **Generated distributions serve GitHub Copilot and Claude Code.** `scripts/build_dist.py` generates `.github/skills/` for GitHub Copilot and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. Neither generated tree is hand-edited, and `build_dist.py --check` exits non-zero when either tree differs from `.agents/skills/`.
 - **The skill set is implicit.** Every `.agents/skills/<name>/` directory carrying a `SKILL.md` is a skill, and the generated `plugin.json` derives its list from those directories, so adding or retiring a skill edits no manifest by hand. `marketplace.json` names the plugin, not the skills, and is untouched by ordinary lifecycle work.
 - **`scripts/skills_install.py`, run from a hub checkout, installs both forms per machine**: an overlay copy into `~/.agents/skills/` for Codex and opencode, marked per skill so a retired skill is removed on the next run and a foreign skill is never touched, and a user-scope plugin install for Claude Code via the `claude` CLI. Each run stamps the hub commit into `~/.agents/skills-install-stamp.json`, and `--report` reads that stamp against the checkout and exits non-zero when the machine is behind. The install is global per user, and per-repo pinning is a settled non-goal (`docs/fleet-map.md` "Skills Install Model").
 
@@ -28,13 +28,13 @@ A skill surfaces at a trigger moment. A rule that binds every action all the tim
 3. **Author the body per the `comment-and-doc-style` skill**: LF (the repo default), present tense, ASCII tiers, no semicolon in prose. Name hub paths as plain code spans rather than repo-relative links, because an installed copy resolves no repo path, and say "from a hub checkout" for anything the reader must run.
 4. **Split bulk into `references/`** when the source doc is large: the SKILL.md carries the summary and the binding rules, and each `references/*.md` carries one topic read on demand, the shape `comment-and-doc-style` uses.
 5. **Apply the doc-packaging pattern below in the same change** when the skill packages a law doc or one of its sections.
-6. **Regenerate and commit both trees together**: `python3 scripts/build_dist.py`, then commit the source and the regenerated `.claude-plugin/` in one commit. CI runs `--check` on every pull request and fails a desynced pair. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
+6. **Regenerate and commit all trees together**: `python3 scripts/build_dist.py`, then commit the source and both generated trees in one commit. CI runs `--check` on every pull request and fails a desynced distribution. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
 7. **Record the surfacing**: annotate the `AGENTS.md` "Where the Rules Live" row when the skill packages a GOVERNANCE section, or its closing paragraph when the skill is new content, so the map stays the one place coverage is read from.
 8. **Refresh the machines after merge**: re-run `python3 scripts/skills_install.py` per machine, the cadence `docs/host-setup.md` "Fleet Skills Install" states. Until then every machine serves the previous skill set, which `--report` says.
 
 ## Changing or Retiring a Skill
 
-- **Edit only the source tree.** Any content change under `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
+- **Edit only the source tree.** Any skill-content change under `.github/skills/` or `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
 - **Retiring is deleting the source directory and regenerating.** The derived `plugin.json` list shrinks with it, and the installer's per-skill markers remove the retired skill from `~/.agents/skills/` on each machine's next run.
 - **A deletion sweeps the prose that references the skill**, in the same change rather than as follow-up: the `AGENTS.md` map row or paragraph naming it, any law-doc packaging pointer to it, and any sibling skill that disambiguates against it. A law-doc section that had moved its full rules into the skill takes them back, or is retired with it, so no rule is silently lost with the skill that carried it.
 - **Renaming is a retire plus a create** as far as the installer's markers and the plugin list are concerned, so sweep references the same way.

.claude-plugin/fleet-skills/.claude-plugin/plugin.json

@@ -9,6 +9,7 @@
  "./skills/agent-conduct",
  "./skills/audit-a-repo",
  "./skills/carried-instruction-file-guard",
+ "./skills/code-review",
  "./skills/comment-and-doc-style",
  "./skills/copilot-instructions-keeper",
  "./skills/dotnet-codestyle",

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-2796eec540f960cb
+cf555123c5d2982d

.claude-plugin/fleet-skills/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.claude-plugin/fleet-skills/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/README.md

@@ -2,6 +2,6 @@
 
 Canonical source for the fleet's Claude Code / opencode / Codex Skills, one directory per skill: `<name>/SKILL.md` plus optional `scripts/` and `references/`. This is the only place a skill's content is hand-authored. Everything else derived from it is generated, never hand-edited.
 
-Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
+Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. GitHub Copilot discovers repository skills under `.github/skills/`. `scripts/build_dist.py` generates both the GitHub tree and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
 
 See `AGENTS.md` for how a repo depends on these skills and `scripts/README.md` for `build_dist.py` and the installer. The procedure for creating, changing, or retiring a skill is the `skill-lifecycle` skill (`skill-lifecycle/SKILL.md` here), which this README defers to.

.agents/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.agents/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/pr-review-conduct/SKILL.md

@@ -13,9 +13,9 @@ description: >-
  full diff, or left a suppressed low-confidence finding, which opens no thread at all,
  unanswered. Also triggers when a review loop looks stuck
  (no review landing, findings that keep reappearing) or when deciding a finding is real, false,
- deferred, or a deliberate decline. Provider-specific mechanics (GitHub Copilot's request/poll/
-reply API calls) live in .github/copilot-instructions.md's "GitHub Copilot Review Runbook,"
-this skill is the contract that runbook implements, not a replacement for it.
+ deferred, or a deliberate decline. Provider-specific mechanics are implemented by
+scripts/pr_review.py and bootstrapped by .github/copilot-instructions.md. This skill is the
+ contract those surfaces implement, not a replacement for them.
 ---
 
 # PR Review Conduct
@@ -134,13 +134,11 @@ head-scoped query while still unanswered.
 - A finding is judged real but should not be fixed. That decision is never the agent's alone.
 - An architectural redesign is proposed rather than a bug fix.
 
-## Mechanics live elsewhere
+## Mechanics Live Elsewhere
 
-This skill is the provider-agnostic contract. For the actual GitHub API calls, requesting a
-Copilot review, polling for it, matching the suppressed-findings heading (its wording has moved
-more than once), verifying head-SHA and diff coverage, replying and resolving threads without a
-hand-typed id, see `.github/copilot-instructions.md` "GitHub Copilot Review Runbook" in the repo
-being worked in, and reach for `scripts/pr_review.py` (hub-hosted, invoked from a hub checkout)
-before hand-rolling any of it. `status` reports coverage, threads, suppressed findings, and shapes
-in one call, `wait` backs off in-process, and `reply` resolves a thread by matching the finding's
-own words rather than a line number a fix push can move.
+This skill is the provider-agnostic contract. Use `scripts/pr_review.py` from a hub checkout for
+the GitHub-specific API operations. `status` reports coverage, threads, body-only findings, and
+shapes in one call. `wait` requests and polls in-process. `reply` resolves a thread by matching
+the finding's own words instead of a line number a fix push can move. The repository's
+`.github/copilot-instructions.md` bootstraps Copilot into the `code-review` skill and its stable
+coverage marker. Do not reconstruct the API operations by hand.

.agents/skills/skill-lifecycle/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-lifecycle
 description: >-
- Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/ or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated plugin desyncs the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
+ Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .github/skills/ and .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/, .github/skills/, or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated distributions desync the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
 ---
 
 # Skill Lifecycle
@@ -13,7 +13,7 @@ The agent most likely to get a skill wrong is the one editing a skill, and befor
 ## The Pipeline
 
 - **`.agents/skills/<name>/SKILL.md` is the only hand-authored source**, with optional `references/` and `scripts/` directories beside it. Codex and opencode read this tree directly, project-local, and also read the global `~/.agents/skills/` copy the installer materializes.
-- **Claude Code never scans that path.** `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. The generated tree is never hand-edited, and `build_dist.py --check` exits non-zero when it was built from different source bytes than `.agents/skills/` currently holds.
+- **Generated distributions serve GitHub Copilot and Claude Code.** `scripts/build_dist.py` generates `.github/skills/` for GitHub Copilot and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. Neither generated tree is hand-edited, and `build_dist.py --check` exits non-zero when either tree differs from `.agents/skills/`.
 - **The skill set is implicit.** Every `.agents/skills/<name>/` directory carrying a `SKILL.md` is a skill, and the generated `plugin.json` derives its list from those directories, so adding or retiring a skill edits no manifest by hand. `marketplace.json` names the plugin, not the skills, and is untouched by ordinary lifecycle work.
 - **`scripts/skills_install.py`, run from a hub checkout, installs both forms per machine**: an overlay copy into `~/.agents/skills/` for Codex and opencode, marked per skill so a retired skill is removed on the next run and a foreign skill is never touched, and a user-scope plugin install for Claude Code via the `claude` CLI. Each run stamps the hub commit into `~/.agents/skills-install-stamp.json`, and `--report` reads that stamp against the checkout and exits non-zero when the machine is behind. The install is global per user, and per-repo pinning is a settled non-goal (`docs/fleet-map.md` "Skills Install Model").
 
@@ -28,13 +28,13 @@ A skill surfaces at a trigger moment. A rule that binds every action all the tim
 3. **Author the body per the `comment-and-doc-style` skill**: LF (the repo default), present tense, ASCII tiers, no semicolon in prose. Name hub paths as plain code spans rather than repo-relative links, because an installed copy resolves no repo path, and say "from a hub checkout" for anything the reader must run.
 4. **Split bulk into `references/`** when the source doc is large: the SKILL.md carries the summary and the binding rules, and each `references/*.md` carries one topic read on demand, the shape `comment-and-doc-style` uses.
 5. **Apply the doc-packaging pattern below in the same change** when the skill packages a law doc or one of its sections.
-6. **Regenerate and commit both trees together**: `python3 scripts/build_dist.py`, then commit the source and the regenerated `.claude-plugin/` in one commit. CI runs `--check` on every pull request and fails a desynced pair. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
+6. **Regenerate and commit all trees together**: `python3 scripts/build_dist.py`, then commit the source and both generated trees in one commit. CI runs `--check` on every pull request and fails a desynced distribution. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
 7. **Record the surfacing**: annotate the `AGENTS.md` "Where the Rules Live" row when the skill packages a GOVERNANCE section, or its closing paragraph when the skill is new content, so the map stays the one place coverage is read from.
 8. **Refresh the machines after merge**: re-run `python3 scripts/skills_install.py` per machine, the cadence `docs/host-setup.md` "Fleet Skills Install" states. Until then every machine serves the previous skill set, which `--report` says.
 
 ## Changing or Retiring a Skill
 
-- **Edit only the source tree.** Any content change under `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
+- **Edit only the source tree.** Any skill-content change under `.github/skills/` or `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
 - **Retiring is deleting the source directory and regenerating.** The derived `plugin.json` list shrinks with it, and the installer's per-skill markers remove the retired skill from `~/.agents/skills/` on each machine's next run.
 - **A deletion sweeps the prose that references the skill**, in the same change rather than as follow-up: the `AGENTS.md` map row or paragraph naming it, any law-doc packaging pointer to it, and any sibling skill that disambiguates against it. A law-doc section that had moved its full rules into the skill takes them back, or is retired with it, so no rule is silently lost with the skill that carried it.
 - **Renaming is a retire plus a create** as far as the installer's markers and the plugin list are concerned, so sweep references the same way.

.claude-plugin/fleet-skills/.claude-plugin/plugin.json

@@ -9,6 +9,7 @@
  "./skills/agent-conduct",
  "./skills/audit-a-repo",
  "./skills/carried-instruction-file-guard",
+ "./skills/code-review",
  "./skills/comment-and-doc-style",
  "./skills/copilot-instructions-keeper",
  "./skills/dotnet-codestyle",

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-2796eec540f960cb
+cf555123c5d2982d

.claude-plugin/fleet-skills/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.claude-plugin/fleet-skills/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/README.md

@@ -2,6 +2,6 @@
 
 Canonical source for the fleet's Claude Code / opencode / Codex Skills, one directory per skill: `<name>/SKILL.md` plus optional `scripts/` and `references/`. This is the only place a skill's content is hand-authored. Everything else derived from it is generated, never hand-edited.
 
-Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
+Codex and opencode read this directory directly (`.agents/skills/<name>/SKILL.md`), no install step required, walking from a downstream repo's working directory up to its own repository root. Claude Code does not scan this path. GitHub Copilot discovers repository skills under `.github/skills/`. `scripts/build_dist.py` generates both the GitHub tree and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`.
 
 See `AGENTS.md` for how a repo depends on these skills and `scripts/README.md` for `build_dist.py` and the installer. The procedure for creating, changing, or retiring a skill is the `skill-lifecycle` skill (`skill-lifecycle/SKILL.md` here), which this README defers to.

.agents/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.agents/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot

.agents/skills/pr-review-conduct/SKILL.md

@@ -13,9 +13,9 @@ description: >-
  full diff, or left a suppressed low-confidence finding, which opens no thread at all,
  unanswered. Also triggers when a review loop looks stuck
  (no review landing, findings that keep reappearing) or when deciding a finding is real, false,
- deferred, or a deliberate decline. Provider-specific mechanics (GitHub Copilot's request/poll/
-reply API calls) live in .github/copilot-instructions.md's "GitHub Copilot Review Runbook,"
-this skill is the contract that runbook implements, not a replacement for it.
+ deferred, or a deliberate decline. Provider-specific mechanics are implemented by
+scripts/pr_review.py and bootstrapped by .github/copilot-instructions.md. This skill is the
+ contract those surfaces implement, not a replacement for them.
 ---
 
 # PR Review Conduct
@@ -134,13 +134,11 @@ head-scoped query while still unanswered.
 - A finding is judged real but should not be fixed. That decision is never the agent's alone.
 - An architectural redesign is proposed rather than a bug fix.
 
-## Mechanics live elsewhere
+## Mechanics Live Elsewhere
 
-This skill is the provider-agnostic contract. For the actual GitHub API calls, requesting a
-Copilot review, polling for it, matching the suppressed-findings heading (its wording has moved
-more than once), verifying head-SHA and diff coverage, replying and resolving threads without a
-hand-typed id, see `.github/copilot-instructions.md` "GitHub Copilot Review Runbook" in the repo
-being worked in, and reach for `scripts/pr_review.py` (hub-hosted, invoked from a hub checkout)
-before hand-rolling any of it. `status` reports coverage, threads, suppressed findings, and shapes
-in one call, `wait` backs off in-process, and `reply` resolves a thread by matching the finding's
-own words rather than a line number a fix push can move.
+This skill is the provider-agnostic contract. Use `scripts/pr_review.py` from a hub checkout for
+the GitHub-specific API operations. `status` reports coverage, threads, body-only findings, and
+shapes in one call. `wait` requests and polls in-process. `reply` resolves a thread by matching
+the finding's own words instead of a line number a fix push can move. The repository's
+`.github/copilot-instructions.md` bootstraps Copilot into the `code-review` skill and its stable
+coverage marker. Do not reconstruct the API operations by hand.

.agents/skills/skill-lifecycle/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-lifecycle
 description: >-
- Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/ or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated plugin desyncs the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
+ Governs the lifecycle of the fleet's own skills in ptr727/ProjectTemplate: creating, changing, splitting, and retiring a skill under .agents/skills/, the source-versus-generated split with .github/skills/ and .claude-plugin/, the regenerate and --check semantics of scripts/build_dist.py, the install and stamp semantics of scripts/skills_install.py, the doc-packaging pattern that keeps a law doc and its skill in agreement, and the trigger-description conventions that make a skill fire. Use this whenever about to create, edit, move, or delete anything under .agents/skills/, .github/skills/, or .claude-plugin/, whenever packaging a doc or a doc section as a skill, and whenever deciding whether a topic deserves a skill at all. Triggers even when the edit looks trivial, such as fixing a typo in one SKILL.md, because the generated distributions desync the moment the source changes without a build_dist.py run, and CI fails the pull request on exactly that. Hub-context only, since .agents/skills/ exists only in the hub.
 ---
 
 # Skill Lifecycle
@@ -13,7 +13,7 @@ The agent most likely to get a skill wrong is the one editing a skill, and befor
 ## The Pipeline
 
 - **`.agents/skills/<name>/SKILL.md` is the only hand-authored source**, with optional `references/` and `scripts/` directories beside it. Codex and opencode read this tree directly, project-local, and also read the global `~/.agents/skills/` copy the installer materializes.
-- **Claude Code never scans that path.** `scripts/build_dist.py` generates a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. The generated tree is never hand-edited, and `build_dist.py --check` exits non-zero when it was built from different source bytes than `.agents/skills/` currently holds.
+- **Generated distributions serve GitHub Copilot and Claude Code.** `scripts/build_dist.py` generates `.github/skills/` for GitHub Copilot and a Claude-plugin-compatible copy at `.claude-plugin/fleet-skills/`, published through `.claude-plugin/marketplace.json`. Neither generated tree is hand-edited, and `build_dist.py --check` exits non-zero when either tree differs from `.agents/skills/`.
 - **The skill set is implicit.** Every `.agents/skills/<name>/` directory carrying a `SKILL.md` is a skill, and the generated `plugin.json` derives its list from those directories, so adding or retiring a skill edits no manifest by hand. `marketplace.json` names the plugin, not the skills, and is untouched by ordinary lifecycle work.
 - **`scripts/skills_install.py`, run from a hub checkout, installs both forms per machine**: an overlay copy into `~/.agents/skills/` for Codex and opencode, marked per skill so a retired skill is removed on the next run and a foreign skill is never touched, and a user-scope plugin install for Claude Code via the `claude` CLI. Each run stamps the hub commit into `~/.agents/skills-install-stamp.json`, and `--report` reads that stamp against the checkout and exits non-zero when the machine is behind. The install is global per user, and per-repo pinning is a settled non-goal (`docs/fleet-map.md` "Skills Install Model").
 
@@ -28,13 +28,13 @@ A skill surfaces at a trigger moment. A rule that binds every action all the tim
 3. **Author the body per the `comment-and-doc-style` skill**: LF (the repo default), present tense, ASCII tiers, no semicolon in prose. Name hub paths as plain code spans rather than repo-relative links, because an installed copy resolves no repo path, and say "from a hub checkout" for anything the reader must run.
 4. **Split bulk into `references/`** when the source doc is large: the SKILL.md carries the summary and the binding rules, and each `references/*.md` carries one topic read on demand, the shape `comment-and-doc-style` uses.
 5. **Apply the doc-packaging pattern below in the same change** when the skill packages a law doc or one of its sections.
-6. **Regenerate and commit both trees together**: `python3 scripts/build_dist.py`, then commit the source and the regenerated `.claude-plugin/` in one commit. CI runs `--check` on every pull request and fails a desynced pair. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
+6. **Regenerate and commit all trees together**: `python3 scripts/build_dist.py`, then commit the source and both generated trees in one commit. CI runs `--check` on every pull request and fails a desynced distribution. `python3 scripts/tests/test_build_dist.py` covers the generator itself.
 7. **Record the surfacing**: annotate the `AGENTS.md` "Where the Rules Live" row when the skill packages a GOVERNANCE section, or its closing paragraph when the skill is new content, so the map stays the one place coverage is read from.
 8. **Refresh the machines after merge**: re-run `python3 scripts/skills_install.py` per machine, the cadence `docs/host-setup.md` "Fleet Skills Install" states. Until then every machine serves the previous skill set, which `--report` says.
 
 ## Changing or Retiring a Skill
 
-- **Edit only the source tree.** Any content change under `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
+- **Edit only the source tree.** Any skill-content change under `.github/skills/` or `.claude-plugin/` that did not come from a `build_dist.py` run is a defect, whatever it fixes.
 - **Retiring is deleting the source directory and regenerating.** The derived `plugin.json` list shrinks with it, and the installer's per-skill markers remove the retired skill from `~/.agents/skills/` on each machine's next run.
 - **A deletion sweeps the prose that references the skill**, in the same change rather than as follow-up: the `AGENTS.md` map row or paragraph naming it, any law-doc packaging pointer to it, and any sibling skill that disambiguates against it. A law-doc section that had moved its full rules into the skill takes them back, or is retired with it, so no rule is silently lost with the skill that carried it.
 - **Renaming is a retire plus a create** as far as the installer's markers and the plugin list are concerned, so sweep references the same way.

.claude-plugin/fleet-skills/.claude-plugin/plugin.json

@@ -9,6 +9,7 @@
  "./skills/agent-conduct",
  "./skills/audit-a-repo",
  "./skills/carried-instruction-file-guard",
+ "./skills/code-review",
  "./skills/comment-and-doc-style",
  "./skills/copilot-instructions-keeper",
  "./skills/dotnet-codestyle",

.claude-plugin/fleet-skills/.source-digest

@@ -1 +1 @@
-2796eec540f960cb
+cf555123c5d2982d

.claude-plugin/fleet-skills/skills/code-review/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: code-review
+description: >-
+ Reviews a pull request or change set against the repository's contracts, with explicit diff
+ coverage and no suppressed findings. Use this whenever asked to review code, a pull request,
+ a patch, or a proposed change, and whenever GitHub Copilot performs code review. Triggers even
+ when the diff is documentation-only or workflow-only, because the review must load the
+ applicable general, language, documentation, and workflow skills before judging the change.
+---
+
+# Code Review
+
+## Establish the Contract
+
+1. Read the root `AGENTS.md` and the sections it routes to for the changed paths.
+2. Read the complete diff and enumerate every changed file before forming findings.
+3. Load every applicable sibling skill from the current skill distribution:
+ - `comment-and-doc-style` for Markdown, prose, comments, commit messages, and PR titles.
+ - `dotnet-codestyle` for C# and .NET changes.
+ - `python-codestyle` for Python changes.
+ - `shell-codestyle` for shell changes.
+ - `workflow-ci-contract` for GitHub Actions and CI/CD changes.
+4. Treat a missing executable on `PATH` as no evidence that its check is unavailable. Read the
+ repository's documented local invocation before reporting a check as skipped.
+
+Do not substitute a familiar convention for the repository's written contract. Report a
+conflict between instructions instead of silently choosing one.
+
+## Review the Change
+
+Review for correctness, regressions, security, compatibility, error handling, concurrency,
+resource lifetime, tests, and contract drift. Follow data and control flow beyond the edited
+lines when the behavior depends on unchanged callers or consumers.
+
+For each candidate finding:
+
+1. Verify it against the current head tree, not an unfetched checkout or the base branch.
+2. Identify the concrete failing behavior and the conditions that reach it.
+3. Confirm that the repository does not already prevent it elsewhere.
+4. Prefer one root-cause finding over several symptoms of the same defect.
+5. Omit pure preferences that no repository rule or user-visible risk supports.
+
+Review carried fleet content by intent and fidelity. A byte-locked reference to a path that one
+downstream repository does not carry is not a broken link. A substantive defect in canonical
+content remains a finding, with the fix located at its canonical source.
+
+## Publish Every Finding
+
+Never suppress or hide a finding because confidence is low. Investigate until it is supported
+or discard it. Publish every supported finding as an inline review comment when a changed line
+can anchor it. Use the review body only when no valid inline anchor exists.
+
+Each finding states:
+
+- A concise imperative title with a severity.
+- The file and smallest useful line range.
+- The behavior that fails and the input or state that triggers it.
+- Why the change causes the failure.
+- A bounded direction for the fix when one is known.
+
+Do not report a clean review until every changed file has been read. End the review body with
+exactly one ASCII marker, replacing the numbers with measured counts:
+
+```text
+<!-- fleet-review: reviewed=N changed=N findings=N -->
+```
+
+`reviewed` is the number of changed files actually reviewed. `changed` is the total number of
+changed files. `findings` is the number of published findings, including body-only findings.
+Never emit `reviewed=changed` as a placeholder. If full coverage is impossible, emit the actual
+counts and explain the limitation in the review body.

.claude-plugin/fleet-skills/skills/copilot-instructions-keeper/SKILL.md

@@ -18,10 +18,10 @@ description: >-
 
 ## Why this exists
 
-`.github/copilot-instructions.md` is read directly by the GitHub Copilot review bot, which
-cannot read a `SKILL.md`. Unlike other carried governance content, its rule text is never
-pointer-ized into a skill, this file always stays fully intact in every repo that carries it.
-This skill is about maintaining that file's carried copy, not a substitute for it.
+`.github/copilot-instructions.md` is read directly by GitHub Copilot and bootstraps the shared
+`AGENTS.md` instruction set and review-focused skills. Its Copilot-specific rules stay fully
+intact in every repo that carries it. This skill maintains that carried copy, it does not replace
+the bootstrap.
 
 `spec/files.json` declares it `intent` fidelity, `whole: true`, covering three named sections
 (`Commit Messages and Pull Request Titles`, `Reviewing Carried Fleet Content`, `GitHub Copilot