dev-all
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Process issues sequentially: /dev per issue in isolated sub-agent → CI wait → merge → next
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Aurealibe/claude-configtheir own version, first seen Jul 10, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Aurealibe/claude-config★ 68same 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- auditSkill
- decomposeSkill
- dev-investigateSkill
- devSkill
- digSkill
- investigateSkill
- prSkill
- reviewSkill
- tech-debtSkill
- update-docsSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
Read the project's CLAUDE.md and look for ## Core Values section
- Distinctive: line 53
If user chooses to proceed without, log a warning in the final report
- Very specific: line 86
Check issue bodies for: blocked by #N, depends on #N, after #N
- Distinctive: line 105
Ask user to confirm before proceeding.
- Distinctive: line 111
Create a master task tracker:
- Distinctive: line 141
After the sub-agent completes, validate the result before proceeding to merge:
- Very specific: line 143
Read workspace/{issue}/review.json to get the structured review output
- Distinctive: line 168
Ask: skip this issue and continue, or stop?
- Very specific: line 194
When the user invokes /dev-all with /goal, the entire batch runs autonomously:
- Distinctive: line 203
Stop only on 3 consecutive failures
≈ “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.
Files
/dev-all — Sequential Issue Processing
Process multiple GitHub Issues sequentially. Each issue runs /dev in an isolated sub-agent, then waits for CI and merges before proceeding to the next.
Arguments: $ARGUMENTS
Why Per-Issue (not Single Branch)?
Each issue gets its own branch, PR, and merge cycle:
- Clean git history: each PR is atomic and reviewable
- CI validates each change independently
- Merge conflicts are impossible: each issue starts from latest main
- Rollback is easy: revert a single PR, not a batch
Step 0: Core Value Check (GATE)
- Read the project's
CLAUDE.mdand look for## Core Valuessection - If missing: Warn the user that Core Values are undefined. Ask if they want to:
- Define Core Values now (recommended)
- Proceed without the filter (not recommended — risk of feature bloat)
- If user chooses to proceed without, log a warning in the final report
Step 1: Resolve Target Issues
If $ARGUMENTS is provided: Extract issue numbers.
If empty: Fetch all open issues:
gh issue list --state open --json number,title,labels,body --limit 1001a. Filter Issues
- Skip issues labeled
won't— these are explicitly decided not to implement - Skip issues listed in CLAUDE.md
## Won't Do— cross-reference issue titles
Step 2: Parallel Investigation (Read-Only)
Launch parallel Explore agents (one per issue) to quickly understand scope:
Each agent:
gh issue view {NUMBER} --json title,body,labels,comments- Grep/Glob to find related code
- Return: summary, affected files, estimated scope, dependencies
Step 3: Dependency Analysis & Order
3a. Detect Dependencies
Check issue bodies for: blocked by #N, depends on #N, after #N
3b. Execution Order
Topological sort:
- Independent issues first (ascending by number)
- Dependent issues after their dependencies
- Circular dependencies → skip, report
── AskUserQuestion: Execution Plan ──
Present:
- Ordered list of issues
- Dependencies detected
- Skipped issues (with reasons — including
won'tlabel and Won't Do matches) - Estimated scope per issue
- Core Value alignment per issue (if Core Values are defined)
Ask user to confirm before proceeding.
Step 4: Sequential Issue Loop
Create a master task tracker:
TaskCreate for each issue: "#{number}: {title}"For each issue (in order):
4a. Pull latest main
git checkout main && git pull origin main4b. Run /dev in isolated sub-agent (autonomous via /goal)
Agent(
prompt: "/goal 'Issue #{issue_number} is resolved: tests pass, review has no Critical findings, and PR is created' /dev #{issue_number}",
model: "opus",
isolation: "worktree"
)The sub-agent:
- Gets a fresh context (no pollution from previous issues)
- Works in an isolated git worktree (no file conflicts)
- Runs the full /dev workflow autonomously via /goal
- Skips AskUserQuestion confirmations (proceeds with best judgment)
- Returns: structured result with PR URL, review status, and counts
4b-result. Review Validation
After the sub-agent completes, validate the result before proceeding to merge:
- Read
workspace/{issue}/review.jsonto get the structured review output - Parse the sub-agent's return value for review status
Decision logic:
| Review Status | Action |
critical (critical_count > 0) | Skip this issue. Report to user: "#{issue} has {N} critical findings — skipping." Mark task as failed. Proceed to next issue. |
warnings (warning_count > 0) | Report to user. AskUserQuestion: "#{issue} PR has {N} unresolved warnings. Merge anyway?" If yes → proceed. If no → skip. |
clean | Proceed to auto-merge. |
Sub-agent failed (status: "failed") | Skip this issue. Report failure reason. Proceed to next issue. |
4c. Enable auto-merge
gh pr merge {PR_URL} --auto --merge --delete-branch4d. Wait for merge
Poll until merged (check every 30 seconds, timeout 15 minutes):
STATE=$(gh pr view {PR_URL} --json state -q '.state')If CI fails:
- Report the failure to user
- Ask: skip this issue and continue, or stop?
4e. Mark task completed and proceed
Step 5: Final Report
## Batch Development Summary
| # | Issue | PR | Status |
|---|-------|----|--------|
| 1 | #{42} Title | PR_URL | Merged |
| 2 | #{43} Title | PR_URL | Merged |
| 3 | #{44} Title | — | Skipped (CI failed) |
Completed: N / M issuesMark all tasks completed.
Autonomous Mode (/goal)
When the user invokes /dev-all with /goal, the entire batch runs autonomously:
/goal "All issues in $ARGUMENTS are resolved: each has a merged PR or a documented skip reason"In autonomous mode:
- Skip
AskUserQuestionconfirmations — proceed with best judgment - On CI failure: skip the issue and continue (don't stop)
- Stop only on 3 consecutive failures
Error Handling
| Situation | Action |
| Issue not found | Skip, warn in report |
| Circular dependency | Skip affected issues, report |
| Sub-agent /dev fails | Ask user: skip or stop |
| CI fails | Ask user: skip or stop |
| Merge conflict | Ask user: skip or stop |
| 3 consecutive failures | Stop, report to user |
| Auto-merge timeout (15min) | Report, ask user |
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.

