| name | shannon-coordination-audit |
| description | Run Shannon's read-only cross-team coordination audit for gllvmTMB branches, pull requests, working-tree state, dev-log handoffs, and after-task report coverage before handoffs, merges, or multi-PR fan-out. |
Shannon Coordination Audit
Use this skill when Codex, Claude Code, or the maintainer needs to
check cross-team state: before a working-tree switch, before merge
sequencing, after several agents opened PRs, or at the end of a work
session.
Shannon is read-only. Do not edit files, merge PRs, rerun CI, or
resolve conflicts. Report PASS, WARN, or FAIL with concrete
evidence and the smallest recommended next action.
Checks
- Working tree: current branch, uncommitted files, untracked
files, and whether local changes belong to the active branch.
- PR census: open PR count, branch names, authorship signal when
available, mergeability, CI state, and likely merge order.
- File overlap: PRs touching the same coordination files
(
AGENTS.md, CLAUDE.md, CONTRIBUTING.md, ROADMAP.md,
docs/dev-log/check-log.md, docs/dev-log/decisions.md,
docs/dev-log/after-task/) or the same implementation files.
- After-task coverage: every completed task PR should include an
after-task report in the same branch unless it is a read-only audit
whose report is the audit document itself.
- Message bus: important handoffs should appear in PR comments,
docs/dev-log/check-log.md, docs/dev-log/decisions.md, or an
after-task report, not only in chat.
- Rule drift: current practice should be compared with stated
rules, especially:
- WIP limit (3 open PRs per Claude lane is the soft cap; under 3
is healthy)
- CI pacing (no rapid-fire pushes; wait for the active run to
complete before pushing a follow-up commit)
- Pre-edit lane check (per
AGENTS.md "Multi-Agent
Collaboration", PR #22): gh pr list --state open +
git log --all --oneline --since="6 hours ago" before
editing any shared rule file (AGENTS.md, CLAUDE.md,
ROADMAP.md, CONTRIBUTING.md, docs/dev-log/decisions.md,
docs/dev-log/check-log.md, docs/design/,
docs/dev-log/after-task/, inst/COPYRIGHTS, DESCRIPTION)
- After-task at branch start (per
CONTRIBUTING.md
"Definition of Done", PR #22): the skeleton report goes in
the FIRST commit on the branch, filled in as work proceeds
- Merge authority (per
CLAUDE.md "Collaboration
Rhythm", PR #22): low-risk PRs self-merge (docs, dev-log,
audits, after-task, design docs, CI tweaks, asset
additions, single-article rewrites against an approved
snippet); high-risk PRs (deletions, API changes, formula
grammar, likelihood, TMB, family, broad article rewrites)
wait for maintainer
- Surface review asks explicitly in chat (per
CLAUDE.md
"Collaboration Rhythm", PR #22): do not leave maintainer
review items only in PR descriptions
- Agent-to-agent handoffs in the repo (per
CLAUDE.md
"Collaboration Rhythm", PR #22): use PR comments addressed
to the other agent OR directed lines in
docs/dev-log/check-log.md; not maintainer relay only
Suggested Commands
git status --short --branch
git branch -vv --all
gh pr list --repo itchyshin/gllvmTMB --state open \
--json number,title,headRefName,baseRefName,mergeStateStatus,statusCheckRollup,updatedAt,url
gh run list --repo itchyshin/gllvmTMB --limit 12 \
--json databaseId,displayTitle,workflowName,status,conclusion,headBranch,headSha,url
rg -n "after-task|handoff|checkpoint|Shannon|Rose|Codex|Claude" \
AGENTS.md CLAUDE.md CONTRIBUTING.md ROADMAP.md docs/dev-log
For file overlap, inspect each relevant PR:
gh pr view <number> --repo itchyshin/gllvmTMB --json files,headRefName,title,url
Output
Return:
PASS: cross-team state is consistent and the next action is clear.WARN: work can continue, but merge order, CI state, missing notes,
or open-PR fan-out should be acknowledged.FAIL: a branch switch, merge, deletion, NAMESPACE edit, or broad
implementation would risk losing work or violating the project
rules.
Include:
- current branch and dirty/clean state;
- open PR summary and suggested merge order;
- file-overlap or after-task-report gaps;
- one short next-action recommendation.
