process-issues
Skill7 starsChanged 17 days agoApache-2.0View on GitHub
Run the processing loop over open VCFO GitHub issues - triage, implement through the agent roles, gate, review, land, write back, and report. Runs in the main session, only when the user invokes it.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- everruns/everrunstheir own version, first seen Oct 31, 2026
- everruns/bashkittheir own version, first seen Oct 8, 2026
- maslennikov-ig/claude-code-orchestrator-kittheir own version, first seen Mar 5, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- everruns/bashkit★ 325same name
- maslennikov-ig/claude-code-orchestrator-kit★ 248same name
- everruns/everruns★ 66same 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 repository5 other files it gives its agents.
- VCF Orchestrator AgentAGENTS.md
- CLAUDE.mdCLAUDE.md
- issueSkill
- vcfa-authoringSkill
- vcfa-operationsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read and follow .agents/commands/process-issues.md, orchestrating from this main session.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read and follow .agents/commands/process-issues.md, orchestrating from this main session. Run limit: $ARGUMENTS (default 10).
In Claude Code, each role is the subagent of the same name. Start every coder with isolation: "worktree". Start a wave's coders in parallel, at most 3 per message, which is the concurrency limit in process-issues.md. Start the next one as each returns.
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.