Skip to content

sync: template 1.6.22-1.6.28 (verbatim block) #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pip-install-python wants to merge 1 commit into from
Closed

sync: template 1.6.22-1.6.28 (verbatim block) #24

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .claude/skills/report/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,13 @@ Structure, in order:
6. **Open items** — split by who acts: owner (dashboard/env/merge),
orchestrator (cross-repo), this repo's next pass.

Where the pass consumed a sync spec, per-item dispositions use
exactly these five words: `applied` / `ported-as-contract` /
`already-present` / `not-applicable-because` / `open`. `open` means
the detect fires but the item is deliberately out of this session's
scope — name it under Open items with who acts. Do not invent a
sixth word; the orchestrator's tooling reads these five.

Anti-patterns, all observed in the fleet and all rejected on
receipt: "should work" (test it or mark it unverified); summary
claims without artifacts; green CI presented as deploy proof when
Expand Down
Loading
Loading