Repository navigation
chore(skills): restore autonomous-run skill pack deleted in #213 - #222
Conversation
The auto-merge-and-composition-safety, dormant-flip-and-rollback, instrument-dont-guess, swarm-blockers-and-gate-scoreboard, and tiered-acceptance skills were accidentally removed in #213 (slack-comms persona pack) but prpm.json still references all of them at .agentworkforce/workforce/skills/. Restored verbatim from 74f881b^. (autonomous-actor.json was intentionally relocated to packages/persona-autonomous-actor and is not restored here.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI. |
|
Warning Review limit reached
More reviews will be available in 41 minutes and 27 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a comprehensive set of operational skills for autonomous runs, covering guidelines for auto-merging, authoring run contracts, managing dormant flips and rollbacks, implementing diagnostics, swarming blockers, and establishing tiered acceptance criteria. The review feedback focuses on ensuring terminology and state consistency across these skill documents, such as standardizing the 'orchestrator' role, aligning blocking merge states, and correcting hyphenation for terms like 'deep proof' and 'smoke proof'.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| Agent-to-agent message history truncates around 150 characters per turn in some channels; the channel cannot reliably carry full reviews or verdicts. The convention: | ||
|
|
||
| - Each workstream writes its status to `/tmp/ws-<name>-status.md` with the full review/verdict/evidence. | ||
| - The lead aggregates into `/tmp/<run-name>-rollup.md`. |
There was a problem hiding this comment.
To maintain consistent terminology across all skill files, consider changing 'The lead' to 'The orchestrator'. In other files (such as swarm-blockers-and-gate-scoreboard/SKILL.md), this role is consistently referred to as 'the orchestrator', and 'lead' could be confused with 'codex lead'.
Suggested change:
- The orchestrator aggregates into `/tmp/<run-name>-rollup.md`.|
|
||
| The minimum bar that must hold for the agent to merge a PR autonomously. Anything below this bar = manual operator review required. | ||
|
|
||
| - **CI status verified LIVE at merge time** — `gh pr view <n> --json mergeable,mergeStateStatus,statusCheckRollup` against the head SHA at the moment of merge, not against a snapshot taken N minutes ago. `MERGEABLE` + `CLEAN`. Any state below `CLEAN` (`BLOCKED`, `BEHIND`, `UNSTABLE`, `DIRTY`) blocks the merge. |
There was a problem hiding this comment.
For consistency with auto-merge-and-composition-safety/SKILL.md (which lists HAS_HOOKS as a blocking state on line 28), consider adding HAS_HOOKS to the list of states that block the merge here.
Suggested change:
- **CI status verified LIVE at merge time** — `gh pr view <n> --json mergeable,mergeStateStatus,statusCheckRollup` against the head SHA at the moment of merge, not against a snapshot taken N minutes ago. `MERGEABLE` + `CLEAN`. Any state below `CLEAN` (`BLOCKED`, `BEHIND`, `UNSTABLE`, `DIRTY`, `HAS_HOOKS`) blocks the merge.| Tier-2 ships under reduced proof. The safety net comes from the dormant-flip + per-item-enable pattern (`dormant-flip-and-rollback`): | ||
|
|
||
| - **Dormant by default.** Tier-2 variants are not enabled on merge. | ||
| - **Per-item enable.** The flip mechanism enables variants one at a time (per provider, per model, per region). The operator chooses the rollout order: usually tier-1 first (deep-proof gives high confidence; observe in prod), tier-2 in batches (lower confidence; observe more carefully). |
There was a problem hiding this comment.
Consider using 'deep proof' (without the hyphen) to match the noun phrase usage in the rest of the document (e.g., 'deep proof on the high-fidelity slice' on line 52) and to maintain consistent hyphenation.
| - **Per-item enable.** The flip mechanism enables variants one at a time (per provider, per model, per region). The operator chooses the rollout order: usually tier-1 first (deep-proof gives high confidence; observe in prod), tier-2 in batches (lower confidence; observe more carefully). | |
| - **Per-item enable.** The flip mechanism enables variants one at a time (per provider, per model, per region). The operator chooses the rollout order: usually tier-1 first (deep proof gives high confidence; observe in prod), tier-2 in batches (lower confidence; observe more carefully). |
|
|
||
| - **Implicit tiering** — "we'll deep-test the important ones and smoke-test the rest" without writing down which is which. Operator-trade-off is never explicit; coverage becomes wishful. | ||
| - **Hand-maintained tier lists.** Drift = silent regression. | ||
| - **Smoke-proof masquerading as full proof** — a tier-2 variant's smoke test labeled "passed" in the report without the tier distinction noted. Hides the trade-off from anyone reading the report later. |
There was a problem hiding this comment.
Consider using 'Smoke proof' (without the hyphen) to match the noun phrase usage in the rest of the document (e.g., 'smoke proof on the tail' on line 52) and to maintain consistent hyphenation.
| - **Smoke-proof masquerading as full proof** — a tier-2 variant's smoke test labeled "passed" in the report without the tier distinction noted. Hides the trade-off from anyone reading the report later. | |
| - **Smoke proof masquerading as full proof** — a tier-2 variant's smoke test labeled "passed" in the report without the tier distinction noted. Hides the trade-off from anyone reading the report later. |
| - **Hand-maintained tier lists.** Drift = silent regression. | ||
| - **Smoke-proof masquerading as full proof** — a tier-2 variant's smoke test labeled "passed" in the report without the tier distinction noted. Hides the trade-off from anyone reading the report later. | ||
| - **Skipping the per-item-enable pattern.** Tiered acceptance without per-item enable means a bad tier-2 variant takes down all variants together. The trade-off is no longer mitigated. | ||
| - **Letting tier-2 enable on merge.** Bypasses the dormant-default safety. If tier-2 is enabled on merge, the smoke proof was effectively full-proof's responsibility; the trade-off was an illusion. |
There was a problem hiding this comment.
Consider using 'tier-1's responsibility' or 'full proof's responsibility' (without the hyphen) to match the terminology defined in the rest of the document (e.g., 'Tier 1 — full proof' on line 22) and to avoid inconsistent hyphenation.
| - **Letting tier-2 enable on merge.** Bypasses the dormant-default safety. If tier-2 is enabled on merge, the smoke proof was effectively full-proof's responsibility; the trade-off was an illusion. | |
| - **Letting tier-2 enable on merge.** Bypasses the dormant-default safety. If tier-2 is enabled on merge, the smoke proof was effectively tier-1's responsibility; the trade-off was an illusion. |
What
Restores the 6 autonomous-run skills that
prpm.jsondeclares under.agentworkforce/workforce/skills/but which were accidentally deleted in #213 (slack-comms persona pack).autonomous-run-contractauto-merge-and-composition-safetydormant-flip-and-rollbackinstrument-dont-guessswarm-blockers-and-gate-scoreboardtiered-acceptanceWhy
#213 removed
.agentworkforce/workforce/skills/autonomous-*(129–143 lines each) as collateral, butprpm.jsonstill references every one of these paths andpackageIds — leaving 6 dangling references. This restores the files verbatim from74f881b^(the commit just before deletion).Not restored
.agentworkforce/workforce/personas/autonomous-actor.jsonwas also removed in #213, but it was intentionally relocated topackages/persona-autonomous-actor/personas/autonomous-actor.jsonand is not referenced byprpm.json, so it is left as-is.🤖 Generated with Claude Code