agentleFS
Sign inStart free
IgorGanapolskyIgorGanapolsky/ThumbGate/.agents/skills/thumbgate-board-loop/SKILL.md

thumbgate-board-loop

Skill29 starsChanged 7 months agoMITView on GitHub

Autonomous ThumbGate Issues+PR wall loop. Classifies every open Issue and PR, update-branches BEHIND green Dependabot, submits READY via pr:manage/Trunk, comments DIRTY and ECI/umbrella issues. Never approve. Never --admin. Auto-invoke on holdup screenshots, 18 open PRs, 4 open issues, 4/4 green Dependabot wall, "what's the holdup". Slash: /thumbgate-board-loop.

Create a free account to mount
Files
SKILL.md

ThumbGate board loop

Goal

Drain the GitHub Issues + PR wall without a CEO screenshot. The list-view 4/4 badge is not mergeable — those Dependabot PRs are usually SUCCESS + BEHIND after a Trunk land.

Constraints

NEVERALWAYS
Approve a PR / --admin / gh pr merge --autonpx thumbgate board-loop --apply --json
Treat 4/4 as READYClassify mss + required checks (test, CodeQL, changeset, Socket, GitGuardian)
Re-pr:manage a live trunk-merge/pr-NSkip; that PR is already queued
Close DIRTY <30dComment needs-rebase once (marker <!-- thumbgate-board-loop -->)
Implement #3690/#3687 LLM adjudicatorECI pause
Dual-edit DIRTY #3650 graph layerLeave it DIRTY
GHA schedule:Event-driven workflow_run + local LaunchAgent (CodeQL-only schedule policy)

Reference

  • scripts/thumbgate-board-loop.js
  • scripts/pr-manager.js
  • .github/workflows/agent-automerge.yml (must resolve workflow_run.head_sha + dependabot/*)
  • /thumbgate-pr-queue-autopilot · /thumbgate-issues-board-hygiene · /eci-thumbgate-ip-wall

Examples (show, don't tell)

Weak: Paste the 18-open screenshot and ask which PR to merge.

Gold:

$ npx thumbgate board-loop --json
counts.behind=8 counts.dirty=8 trunkQueued=[3874]
$ npx thumbgate board-loop --apply --max-update-branch=1 --json
# gh pr update-branch 3873

Procedures

npx thumbgate board-loop --json
npx thumbgate board-loop --apply --json
npm run test:board-loop
  1. Inventory open PRs + Issues.
  2. Skip trunk-merge drafts.
  3. One BEHIND green update-branch per tick (serial — each land re-BEHINDs siblings).
  4. One READY pr-manager / Trunk submit per tick.
  5. Comment Issues: ECI pause vs IMPLEMENT residual vs umbrella.
  6. Never approve.

Rubric

  • gold classify: SUCCESS+BEHIND → update_branch
  • trunk-merge draft → skip
  • --apply never emits APPROVE / --admin / --auto
  • doctor: npm run test:board-loop PASS
  • evidence: command output in the same turn

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free