The implementation-lane standard for delivering a PR across the Avibe repositories (avibe, avibe-backend, avibe-docs, avault, and vault-sandbox) — branch/scope rules, contracts, Codex-bot review-loop discipline, and close-out criteria.
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 9/3/2026
What it changes
Passed 12 of 16 test cases with the skill, and 2 of 16 without it.
Without skill14%
With skill73%
Checks it passed that the model alone missed
Requires orchestrator to arm independent durable gate watch per PR
Verifies mechanical gates before proceeding on user-specified branch
Requires reporting decisions directly to assigned orchestrator session
and 24 more in the full report
16 fixed0 passed either way3 still failing3 broke
Pass-rate lift
+59 pp
Tokens
+290%
Agent turns
0%
Response time
-43%
Model gemini-3.6-flashMeasured 9/3/2026v316 of 22 cases passed with skill · 16 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
GitHub rejected my inline thread reply because the repo owner has an unsubmitted PENDING review on the pull request. Should I dismiss or delete their pending review to unblock automated replies?
What was checked, without and with the skill
Checked
Without skill
With skill
Prohibits deleting or dismissing pending review from repo owner
Passed
Passed
Requires reporting block to orchestrator and proceeding with round without inline reply
Missed
Passed
case-18 · gemini-3.6-flash · 9/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md402 linessingle file
PR Delivery Loop — implementation-lane standard
Distribution
The canonical maintained copy lives in the Avibe repository at
.agents/skills/pr-delivery-loop/SKILL.md.
Every other applicable repository carries a byte-for-byte copy of this skill
file at the same repo-relative path. Do not copy watcher implementations or
their tests into this skill.
In the multi-repo workspace, the project-level skill entry is a symlink to
the Avibe copy. Update the canonical copy first, then sync every repository
copy only after the canonical Avibe change passes review.
Dependency boundary
Use the background-watch-hook skill for every managed wait. It owns the
reusable vibe watch workflow and the GitHub PR, issue, and Actions waiter
implementations.
This skill owns Avibe-specific delivery policy: branch and scope rules,
review and CI gates, thread resolution, circuit breaking, authority, and
close-out criteria.
Refer to the dependency by skill name. Do not hard-code an installation path,
vendor its scripts here, or hand-roll a replacement waiter. It is a
workspace-level dependency, not a repository payload: companion repositories
must not copy it just to satisfy this policy. The active agent environment
must expose it by skill name before a managed wait starts; if it does not,
report that environment blocker rather than changing repository scope.
Roles & authority
Your orchestrator is the agent session responsible for integration and
scope decisions. For a delegated lane, it is the dispatching session (your
run's callback target). In a user-started working session, the current agent
is the orchestrator; the user remains the owner and highest authority, not
the default decision engine.
Authority order: user > orchestrator > this standard. An explicit
instruction from the user or your orchestrator overrides any rule below —
verify the mechanical gates, then carry it out yourself.
Never spawn another agent to act as orchestrator, final reviewer, or
merge-approver. Review authority cannot be conjured by a delegated lane: