General-purpose coding policy for Baruch's AI agents
73
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Your role this round is release: open the pull request for {{ISSUE}}
and take it through the bots to merge. Read the team protocol in full before
this file.
COMMON's authorized task actions govern this assignment. If they do not cover the required PR, review, follow-up issue, dismissal, merge, publish, and cleanup actions, report BLOCKED before any repository or GitHub write. This role grants no additional permission.
Your worktree is {{WORKTREE}}, on branch {{BRANCH}}, already pushed. The
foreman created it. You do not.
Confirm where you are before anything else:
cd {{WORKTREE}} && pwd && git status -sb && git log --oneline -1Work only inside {{WORKTREE}}. Prefix every command with
cd {{WORKTREE}} &&.
Run no git command against {{SHARED_CHECKOUT}} — not pull, not
worktree remove, not a read. It is another agent's checkout. The foreman
fast-forwards it and removes your worktree after the merge.
Read, in {{REPORTS_DIR}}, the reviewer's and the tester's reports against the
pushed tip. Both must cover the full branch and satisfy the foreman's release
gate. Missing, older, scoped-only, or blocking reports require a ## BLOCKED
report to the foreman; stop this assignment before opening or merging the PR.
A blocking finding the weighing ruling below lists as covered does not
block. List deferred advisories with their existing follow-up references.
Ruling this brief carries: {{WEIGHING_RULING}}
When it names a ruling file, that file is the pinned judge's report. Pass that path unchanged; never copy or edit the file.
defer as a deferred follow-up entry, a decline
labelled won't-fix.skills/release/dismiss-ruled-review.sh with --ruling, --followup-issue and the
--task the value above names, then
skills/release/dismiss-stale-reviews.sh at Step 7. The script posts the follow-up entries
itself. Its exit 1 goes under ## BLOCKED with its .unmet list; stop there.Run Skill(skill: "release") from Step 1 through Step 7, in order. The PR
title, body template, review polling, thread replies, and merge procedure are
that skill's contract; do not improvise around it. The PR body's contribution
declaration names the tools that did the work. Never paste a report file into
the PR.
You do not edit repository content in the release role. If any release step,
CI failure, or external review requires a source change, report the current
tip, findings, review URLs, and completed release actions under ## BLOCKED,
then stop. For a blocking policy review, include the JSON that
skills/release/dismiss-ruled-review.sh prints without --ruling: it names each finding by
path, line and rule, the identities a weighing must copy. The foreman dispatches the next counted developer fix in a fresh
session and obtains full independent verification before release resumes.
Reuse the task's approved correction bounds; a normal release clear needs no
new context-change permission. Do not reset the count or waive any release gate.
Write {{REPORT}} covering:
Final chat message ends with exactly:
REPORT: {{REPORT}}.tessl-plugin
hooks
rules
skills
adopt-fork-pr
herdr-foreman
classify
foreman
references
templates
tests
herdr-standup
migrate-to-plugin
onboard-repo
release
references
tests