Cut backlog-burndown's Two Narrowing Rows to the Narrowing and Pointer Its Fourteen Restatements - #1384
Conversation
…r Its Fourteen Restatements Class 4 of #1317, one file. "Scope" and "The Two Seats" keep the sentence saying this skill is narrower than the rule and drop the second copy of what the rule says, which is the #1305 shape kept as narrowing. The fourteen other inventory rows against GOVERNANCE.md and AGENTS.md homes become a pointer naming the home by document and heading, with the skill's own consequence kept where it had one. The "Bounding a Prose Group" budget bullet becomes a pointer at local-strict-review "Disposing of Findings", per the maintainer's note on #1323, since #1312 has landed the number it used to restate. Closes on promotion: #1305 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…rose Group The diff pass found step 2 still citing "Bounding a Prose Group" as the discipline that sets a review-round budget, after that section became a pointer at local-strict-review and states no budget of its own. The step keeps its own budget and names no other section for it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ful Fetch The second diff pass found "pushed since" and "deleted since" with no anchor once the restated clause about remote-tracking refs was cut, so the sentence read as since the failed fetch where the blind window starts at the last successful one. Fixed under a one-round grant past the budget. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The third diff pass found the operational paragraph's "so confirm" drawing a cadence question from a premise that no longer states a cadence, and "doing it by proxy is still doing it" binding to nothing once "reaching into a tree" was cut while repeating the list item before it. Both are deletions under a second one-round grant past the budget. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🟢 Approval recommended
The changes consistently replace restatements with accurate pointers to canonical rule homes and the regenerated mirrors/ledger updates align with the updated source.
Pull request overview
This PR continues the “one rule, one home” effort by trimming backlog-burndown’s rule inventory prose down to the narrowing that is specific to this skill, and converting the remaining restatements into pointers to their canonical homes (primarily GOVERNANCE.md and AGENTS.md). It then regenerates the distributed skill mirrors and updates the canonical review ledger entries for the units that were re-read.
Changes:
- Replace rule restatements in
.agents/skills/backlog-burndown/SKILL.mdwith pointers to canonical sections, keeping only the skill-specific narrowing/consequence text. - Regenerate the GitHub Copilot and Claude plugin skill mirrors and update the source digest.
- Refresh
reports/canonical-review.jsonentries (digest/hubCommit/stamp/findings) for the re-reviewed backlog-burndown units.
File summaries
| File | Description |
|---|---|
.agents/skills/backlog-burndown/SKILL.md |
Converts inventory restatements into pointers and tightens the two narrowing rows while preserving skill-specific consequences. |
.github/skills/backlog-burndown/SKILL.md |
Regenerated mirror of the updated skill for GitHub Copilot discovery. |
.claude-plugin/fleet-skills/skills/backlog-burndown/SKILL.md |
Regenerated mirror of the updated skill for the Claude plugin distribution. |
.claude-plugin/fleet-skills/.source-digests/backlog-burndown |
Updates the recorded source digest for the distributed backlog-burndown skill. |
reports/canonical-review.json |
Updates canonical-review ledger entries for the backlog-burndown units that were re-read/recorded on this branch. |
Review details
- Files reviewed: 5/5 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…sh the WORKFLOW.md Reshape (#1397) Closes #1205. Closes #1212. Closes #1240. Closes #1250. Closes #1267. Closes #1268. Closes #1271. Closes #1288. Closes #1305. Closes #1314. Sixteen commits, ten issues. Each was driven as its own feature pull request into `develop`, reviewed by the PR-hosted reviewers, and merged only with CI green and every finding disposed of by one of the five outcomes: fixed, declined on evidence, decided by the maintainer, deferred behind a filed issue, or fixed as a class. ## What this promotes **The one-home include mechanism and its first six classes** (#1317). `scripts/build_dist.py` gained include regions filled from a rule's home and checked by `--check` (#1378), so a Skill carries a rule's whole text without a copy that can drift. Classes 2 to 6 then converted the restatements: `agent-conduct`'s three conduct sections (#1382), `pr-review-conduct`'s five outcomes into `drive-pr` with every step-ref renamed to a heading (#1383), `backlog-burndown`'s two narrowing rows cut to the narrowing with fourteen restatements pointered (#1384), `WORKFLOW.md` section 4 into `workflow-ci-contract` (#1385), and section 2 cut to a pointer at `GOVERNANCE.md` "Workflow YAML Conventions" (#1388). **The `WORKFLOW.md` reshape** (#1311 step 14's six-pull-request sequence, now finished). The verdict clause aligned with section 5's Assessment (#1390), sections 3 and 5 carried into `workflow-ci-contract` as generated includes (#1392), 5A collapsed to a procedure and an evidence rule (#1394), and the preamble decisions settled alongside the reshape of section 4, section 6 and the YAML conventions (#1395). Section 4's two longest items shrank to their outcomes with the displaced knowledge moved rather than deleted, and section 6 now states only what each type adds, carrying no N/A list at all. **The review loop's stop rule and disposition policy** (#1330), rewriting disposal by deletion and committing the condition under which a whole-unit loop ends, which #1267 filed as missing. **The Merge Gate's bound on an out-of-diff prose finding**, with the reviewer footing recorded (#1333), and reviewer bots scoped away from the generated Skill mirrors (#1329) so a mirror's diff is never reviewed in place of its source. **The fleet label set**, declared and applied through `configure.sh` (#1334). **The review ledger and skills digest decoupled from the working tree** (#1328), so concurrent branches no longer conflict in a generated report that cannot be hand-merged. Plus one grouped Dependabot bump, `docker/setup-qemu-action` 4.2.0 to 4.3.0 (#1325). ## What is deliberately not closed `#1311`, `#1317`, `#1206`, `#1367`, `#1369`, `#1370`, `#1371`, `#1386` and `#1237` each still hold findings this work did not settle. #1317 stands at class 6 of fourteen, and #1311's step 17 comment records what the reshape filed rather than fixed. ## Owed on merge `spec/files.json` declares both edited `GOVERNANCE.md` sections at `verbatim` fidelity, so every downstream copy goes stale on this promotion and a fleet resync follows it. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Class 4 of #1317, scoped to one file,
.agents/skills/backlog-burndown/SKILL.md, plus its two generated mirrors and digest.What changed
narrowingrows are cut to the narrowing itself (backlog-burndown restates two cross-cutting rules AGENTS.md says to reference #1305). "Scope" says the run is narrower thanGOVERNANCE.md"Repository Boundaries and Write Safety" requires and no longer repeats what that section says about reads or about the owner bound. "The Two Seats" had no narrowing once the restated rule was cut, since a worker is exactly the dispatched taskAGENTS.md"Session Scope" describes, so its worker bullet is a plain pointer.AGENTS.md"Where the Rules Live" condensation at "Dispatching a Worker" is the skill stating its own procedure, and the skill is the home of that. The restatement isAGENTS.md's paragraph about this skill, which is class 8's deletion-and-pointer work.local-strict-review"Disposing of Findings", since P0: Commit a Stop Condition and Round Budget for the Whole-Unit and Local Review Passes #1312 landed the number the bullet used to state a second time.What did not change
The eight step-refs in this file were class 3 (#1383). The "grant is bounded by the session" and "Closing keywords go on the promotion pull request" statements have no home and stay, per the inventory's class 14 list. The pre-existing findings on #1337 are untouched, this change fixes none of them and states no new claim in their sentences.
Verification
python3 scripts/build_dist.py --check,python3 scripts/prose_lint.py . --diff origin/developwith the CI check list plussentence-length,python3 spec/validate.py: clean.fabletier, one reviewer per unit, recorded inreports/canonical-review.json. Counts are in the pull request's read record below.local-strict-review.Read record,
introducedover total per readTen units read whole at the
fabletier, one reviewer per unit, before the first commit. Round 2 read only the two units round 1's introduced findings changed, round 3 read the one unit the first diff pass's finding changed, round 4, a one-round grant past the budget, read the one unit the second diff pass's finding changed, and round 5, a second deletion-only grant, read the two units the third diff pass's findings changed.The six introduced findings: the worker bullet attributed the one-worktree rule to
AGENTS.md"Session Scope", which never mentions worktrees, the operational paragraph's pointer left "What the model adds ... a direct push" without the clause that anchored it, step 2 of "The Promotion Boundary" still cited "Bounding a Prose Group" as the discipline that sets a budget after that section stopped setting one, the failed-fetch sentence's "pushed since" lost its time anchor when the restated clause was cut, the operational paragraph's "so confirm" drew a cadence question from a premise that no longer stated one, and "doing it by proxy is still doing it" lost its noun when "reaching into a tree" was cut. The first two were fixed before round 2, the third before round 3, which spent the budget, the fourth under the maintainer's first one-round grant before round 4, and the last two, both deletions, under a second grant before round 5. Five of the six are a reference or a connective left standing when the restated clause beside it was deleted, the class 3 curve again, and the third diff pass found two of them on sentences the first two diff passes had read. Every pre-existing finding is on #1337, items 28 to 46, and the repeats of items 3, 13, 15, 22, and 27 are not listed again.Closes on promotion: #1305
🤖 Generated with Claude Code