batch-finish-auto
Skill0 starsChanged 49 days agoNo licenceView on GitHub
Drives the acceptance of a WHOLE executor batch autonomously - discovers which run to take (local runs and the remote VPS runner alike, so no parent id has to be remembered), watches the pm run-epic run, and as each sub reaches a terminal status spawns a subagent that runs the batch-finish procedure for it in an isolated worktree, verifying the worker's ASSUMPTIONs with evidence. Mechanizes the "manual" handoff items it can, owns the visual pass on the project's runtime itself (agents never touch the shared simulator), and leaves only design judgment, product calls and device-only checks for the human. Flags: --sim / --no-sim. Coexists with pm's own auto-chain (finish_mode: auto): a batch whose acceptance already ran headless is DRAINED (visual queue + report review only), never redone, and an armed chain is yielded to, not raced. Use when the user says "/batch-finish-auto", "odbierz caly batch", "dowiez odbiory sam", "zrob odbior wszystkich subow", "odbierz batcha z VPS-a", "domknij to co poszlo na serwerze", "dociagnij wizualia po auto-odbiorze", or leaves a run unattended and wants the acceptances delivered on their return. Can start BEFORE the run exists - it waits out prep rather than failing. For ONE task, use batch-finish.
In this repository21 other files it gives its agents.
- batch-finishSkill
- batch-prepSkill
- claim-checkSkill
- cleaning-pm-tasksSkill
- commit-splitSkill
- developing-featuresSkill
- epic-prepSkill
- executor-retroSkill
- figma-ppSkill
- humanizerSkill
- journal-reviewSkill
- parallel-guardSkill
- pass-toSkill
- pmSkill
- simulator-verifySkill
- solo-prepSkill
- solo-retroSkill
- soloSkill
- taking-overSkill
- timeline-bootstrapSkill
- web-verifySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 11 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
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.

