run-queue
Skill0 starsChanged 7 months agoMITView on GitHub
Create and run an autonomous overnight task queue. Use when the user asks to "run tasks overnight", "queue up work", "create an overnight queue", "batch these tasks", "run this while I sleep", or wants to execute a list of coding tasks sequentially using the local Claude CLI without supervision.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rct-labs/gated-flowtheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rct-labs/gated-flow★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- audit-loopSkill
- check-progressSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Create a YAML file with this structure:
- Very specific: line 43
Always use < /dev/null on claude invocations to prevent stdin consumption
- Very specific: line 44
Do NOT use set -e in the runner (non-zero exits should not kill the loop)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Run Queue
Set up and execute a YAML task queue using the local Claude CLI. Each task runs sequentially, commits to the target branch, and logs output. Completed tasks are tracked so re-runs skip finished work.
Queue File Format
Create a YAML file with this structure:
version: "1"
tasks:
- id: unique-kebab-case-id
priority: P0
repo: backend
estimated_minutes: 20
prompt: |
Detailed instructions for Claude. Include:
- Exact file paths to modify
- What to change and why
- How to test (test commands)
- Commit message to useRunning the Queue
nohup bash devops/cloud-coder/run-local-overnight.sh devops/cloud-coder/overnight-queue.yaml > /tmp/overnight.log 2>&1 &Key Rules
- Always use
< /dev/nullon claude invocations to prevent stdin consumption - Do NOT use
set -ein the runner (non-zero exits should not kill the loop) - Tasks run sequentially to avoid merge conflicts
- Completed task IDs persist in
logs/completed.txtfor idempotent reruns
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.