Skip to content

Commit 8626c86

Browse files
Flossyclaude
Flossy
and
claude
committed
feat: add auto-resolve and auto-review skills
Creates 4 new Claude Code skills for autonomous workflows: Skills created: 1. /auto-resolve - One-shot issue resolution (resolve N issues) 2. /auto-resolve-loop - Continuous issue resolution (infinite loop) 3. /auto-review - One-shot code review (run once, create issues) 4. /auto-review-loop - Continuous code review (scheduled monitoring) Benefits: - Easy activation via slash commands - Self-contained skill definitions - Clear documentation in skill files - Portable across projects Usage examples: - /auto-resolve 5 - Resolve next 5 issues - /auto-resolve-loop priority=high - Continuously resolve P0/P1 issues - /auto-review security - Run security scan once - /auto-review-loop - Schedule daily reviews Each skill includes: - Description and usage - Arguments and examples - Quality requirements - Differences from related skills - Links to full documentation These skills make the auto-resolve and auto-review patterns accessible as simple slash commands instead of requiring the full activation prompt. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
1 parent b05447f commit 8626c86

4 files changed

Lines changed: 417 additions & 132 deletions

File tree

‎.claude/skills/auto-resolve-loop.md‎

Lines changed: 234 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,234 @@
1+
---
2+
name: auto-resolve-loop
3+
description: Continuously resolve GitHub issues until interrupted
4+
---
5+
6+
# Auto-Resolve Loop Skill
7+
8+
Continuously monitor and resolve GitHub issues in an infinite loop.
9+
10+
## What This Skill Does
11+
12+
Enters a **continuous loop** that:
13+
1. **Constantly monitors** open GitHub issues
14+
2. **Picks highest priority** issue available
15+
3. **Implements complete solution** with tests
16+
4. **Validates quality** (tests, formatting, linting)
17+
5. **Commits and pushes** immediately
18+
6. **Closes issue** with detailed summary
19+
7. **IMMEDIATELY moves to next issue** without asking
20+
8. **Continues indefinitely** until interrupted or no issues remain
21+
22+
**This is the "work in your absence" mode.**
23+
24+
## Usage
25+
26+
```bash
27+
# Start continuous loop (runs until interrupted)
28+
/auto-resolve-loop
29+
30+
# Start loop with filters
31+
/auto-resolve-loop priority=high
32+
/auto-resolve-loop label=bug
33+
```
34+
35+
## Arguments
36+
37+
- **priority** (optional): Filter by priority (high, medium, low)
38+
- **label** (optional): Filter by GitHub label
39+
40+
## How to Stop
41+
42+
- **Interrupt Claude Code** (Ctrl+C in CLI, Stop button in UI)
43+
- **Close the session** (safe to stop at any point)
44+
- **Say "stop"** in chat (Claude will finish current issue then stop)
45+
46+
The loop will automatically stop when:
47+
- No more issues match the filter
48+
- Context limit is reached (then auto-summarize and can resume with "continue")
49+
50+
## Behavior
51+
52+
### Loop Iteration
53+
```
54+
LOOP FOREVER:
55+
1. Check open issues: gh issue list --state open
56+
2. If no issues match filter:
57+
- Log: "No matching issues found"
58+
- Sleep 5 minutes
59+
- GOTO step 1
60+
3. Pick highest priority issue
61+
4. Implement solution:
62+
- Read code to understand patterns
63+
- Implement fix/feature
64+
- Write comprehensive tests
65+
5. Validate quality:
66+
- Run tests (must pass)
67+
- Format code
68+
- Verify linting
69+
6. Commit and push immediately:
70+
- Detailed commit message
71+
- Push to remote
72+
7. Close issue with summary
73+
8. GOTO step 1 (no pause, no question)
74+
```
75+
76+
### Quality Gates (Never Skipped)
77+
78+
Every commit MUST pass:
79+
- ✅ All existing tests pass (100%)
80+
- ✅ New tests for new functionality
81+
- ✅ Code formatted
82+
- ✅ Linting passing
83+
- ✅ Zero regressions
84+
85+
**If any gate fails, Claude fixes it before committing.**
86+
87+
### Issue Monitoring
88+
89+
Every 3-5 completed issues, Claude checks for:
90+
- New issues created
91+
- Priority changes
92+
- Label updates
93+
- Obsolete issues to close
94+
95+
This allows the loop to adapt to changing priorities.
96+
97+
## Example Session
98+
99+
```
100+
User: /auto-resolve-loop
101+
102+
Claude:
103+
🔄 Entering auto-resolve loop mode...
104+
Will continuously resolve issues until interrupted.
105+
106+
Press Ctrl+C to stop at any time.
107+
108+
─────────────────────────────────────────
109+
110+
Iteration 1: Checking open issues...
111+
Found 12 open issues.
112+
113+
Resolving #342 (P1): Fix Swing compilation errors
114+
✅ Fixed and pushed (commit: a1b2c3d)
115+
✅ Issue closed
116+
117+
Iteration 2: Checking open issues...
118+
Found 11 open issues.
119+
120+
Resolving #339 (P1): Add semantic version validation
121+
✅ Fixed and pushed (commit: d4e5f6g)
122+
✅ Issue closed
123+
124+
Iteration 3: Checking open issues...
125+
Found 10 open issues.
126+
127+
Resolving #333 (P2): Convert to parameterized tests
128+
✅ Fixed and pushed (commit: h7i8j9k)
129+
✅ Issue closed
130+
131+
... [continues automatically] ...
132+
133+
Iteration 15: Checking open issues...
134+
Found 0 open issues matching filter.
135+
Waiting 5 minutes before re-checking...
136+
137+
Iteration 16: Checking open issues...
138+
Found 1 new issue!
139+
140+
Resolving #350 (P0): Security vulnerability in auth
141+
✅ Fixed and pushed (commit: x9y8z7w)
142+
✅ Issue closed
143+
144+
... [continues indefinitely] ...
145+
146+
[User presses Ctrl+C]
147+
148+
🛑 Auto-resolve loop interrupted.
149+
150+
Session Summary:
151+
- Issues resolved: 47
152+
- Commits pushed: 47
153+
- Time elapsed: 3 hours 12 minutes
154+
- Tests: 412 passing (226 → 412, +186 new)
155+
- Zero regressions
156+
- All issues closed
157+
```
158+
159+
## Differences from /auto-resolve
160+
161+
| Feature | /auto-resolve | /auto-resolve-loop |
162+
|---------|---------------|-------------------|
163+
| Mode | One-shot (N issues) | Continuous (∞) |
164+
| Stops after | N issues | Never / Interrupted |
165+
| Asks for next batch | Yes | No (automatic) |
166+
| Monitors new issues | No | Yes (every 3-5 issues) |
167+
| Best for | Quick fixes (5-20) | Large backlogs (50+) |
168+
| Token usage | Fixed/Predictable | Unbounded |
169+
| "Work in absence" | No | Yes |
170+
171+
## When to Use
172+
173+
**Use /auto-resolve-loop when:**
174+
- ✅ You have a large backlog (50+ issues)
175+
- ✅ You want continuous work while away (lunch, overnight)
176+
- ✅ Your test suite is comprehensive (high confidence)
177+
- ✅ Issues are well-defined with clear acceptance criteria
178+
- ✅ You trust the autonomous workflow
179+
180+
**DON'T use /auto-resolve-loop when:**
181+
- ❌ Your test coverage is <80%
182+
- ❌ Issues are vague or require human judgment
183+
- ❌ You want to review each fix before the next
184+
- ❌ You're testing autonomous mode for the first time
185+
186+
Start with `/auto-resolve` (one-shot) first to build confidence, then graduate to `/auto-resolve-loop`.
187+
188+
## Safety Features
189+
190+
1. **Test-Gated Commits**: Nothing commits unless ALL tests pass
191+
2. **Quality Gates**: Formatting and linting verified before every commit
192+
3. **Immediate Push**: Fast feedback from CI on every commit
193+
4. **Issue Summaries**: Detailed close comments for audit trail
194+
5. **Context Monitoring**: Auto-summarizes when approaching limit
195+
6. **Graceful Stop**: Finishes current issue before stopping
196+
197+
## Resuming After Context Limit
198+
199+
When context limit is reached:
200+
```
201+
Session Summary:
202+
- Issues resolved: 23
203+
- Token usage: 198K/200K (99%)
204+
- Approaching context limit, will summarize...
205+
206+
[Session compacts and summarizes]
207+
208+
To resume auto-resolve loop, say: continue
209+
```
210+
211+
Then just type:
212+
```
213+
continue
214+
```
215+
216+
Claude resumes the loop where it left off.
217+
218+
## Prerequisites
219+
220+
Your project MUST have:
221+
- ✅ Comprehensive test suite (80%+ coverage)
222+
- ✅ Fast tests (<10 seconds total)
223+
- ✅ Automated code formatting
224+
- ✅ Linting/static analysis
225+
- ✅ Well-defined GitHub issues
226+
- ✅ GitHub CLI configured
227+
- ✅ CI/CD pipeline (recommended)
228+
229+
## See Also
230+
231+
- `/auto-resolve` - One-shot issue resolution
232+
- `/auto-review` - One-shot code review
233+
- `/auto-review-loop` - Continuous code review
234+
- [AUTO_RESOLVE_MODE.md](../../AUTO_RESOLVE_MODE.md) - Full documentation

‎.claude/skills/auto-resolve.md‎

Lines changed: 145 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,145 @@
1+
---
2+
name: auto-resolve
3+
description: Automatically resolve GitHub issues (one-shot mode)
4+
---
5+
6+
# Auto-Resolve Skill
7+
8+
Automatically resolve the highest priority GitHub issues with complete solutions.
9+
10+
## What This Skill Does
11+
12+
1. **Checks open GitHub issues** using `gh issue list`
13+
2. **Picks the highest priority** issue (P0 > P1 > P2 > P3, or by age)
14+
3. **Implements a complete solution**:
15+
- Reads relevant code to understand patterns
16+
- Implements the fix/feature
17+
- Writes comprehensive tests (unit + integration)
18+
4. **Validates quality**:
19+
- Runs all tests (must pass)
20+
- Formats code (mvn spotless:apply or equivalent)
21+
- Verifies linting (checkstyle, eslint, etc.)
22+
5. **Commits and pushes immediately**:
23+
- Detailed commit message explaining the change
24+
- Co-authored by Claude
25+
6. **Closes the issue** with detailed summary
26+
7. **Repeats for next N issues** (configurable, default 5)
27+
28+
## Usage
29+
30+
```bash
31+
# Resolve next 5 issues (default)
32+
/auto-resolve
33+
34+
# Resolve next 10 issues
35+
/auto-resolve 10
36+
37+
# Resolve only P0/P1 issues
38+
/auto-resolve priority=high
39+
40+
# Resolve issues with specific label
41+
/auto-resolve label=bug
42+
```
43+
44+
## Arguments
45+
46+
- **Number** (optional, default: 5): How many issues to resolve
47+
- **priority** (optional): Filter by priority (high = P0/P1, medium = P2, low = P3)
48+
- **label** (optional): Filter by GitHub label
49+
50+
## Quality Requirements
51+
52+
Every issue resolution MUST:
53+
- ✅ Have passing tests (100% of existing tests must pass)
54+
- ✅ Include new tests for new functionality
55+
- ✅ Be formatted according to project style
56+
- ✅ Pass all linting checks
57+
- ✅ Have zero regressions
58+
- ✅ Include detailed commit message
59+
- ✅ Update documentation if API changed
60+
61+
## Example Session
62+
63+
```
64+
User: /auto-resolve 3
65+
66+
Claude:
67+
Checking open GitHub issues...
68+
Found 12 open issues.
69+
70+
Resolving #342 (P1): Fix Swing compilation errors
71+
├─ Reading platform-swing-ui module
72+
├─ Fixing 3 AWT API mismatches
73+
├─ Running tests... ✅ 226/226 passing
74+
├─ Formatting code... ✅ Done
75+
├─ Committing... ✅ a1b2c3d
76+
├─ Pushing... ✅ Pushed to main
77+
└─ Closing issue... ✅ Closed with summary
78+
79+
Resolving #339 (P1): Add semantic version validation
80+
├─ Creating SemanticVersion class
81+
├─ Updating ServiceRegistry interface
82+
├─ Writing 20 new unit tests
83+
├─ Running tests... ✅ 246/246 passing
84+
├─ Formatting code... ✅ Done
85+
├─ Committing... ✅ d4e5f6g
86+
├─ Pushing... ✅ Pushed to main
87+
└─ Closing issue... ✅ Closed with summary
88+
89+
Resolving #333 (P2): Convert to parameterized tests
90+
├─ Converting RestartPolicyParserTest
91+
├─ Converting HealthCheckConfigParserTest
92+
├─ Reduced 150 lines of duplicated test code
93+
├─ Running tests... ✅ 246/246 passing
94+
├─ Formatting code... ✅ Done
95+
├─ Committing... ✅ h7i8j9k
96+
├─ Pushing... ✅ Pushed to main
97+
└─ Closing issue... ✅ Closed with summary
98+
99+
✅ Auto-resolve complete:
100+
- Issues resolved: 3
101+
- Commits pushed: 3
102+
- Tests: 246 passing (226 → 246, +20 new)
103+
- Zero regressions
104+
- All issues closed
105+
```
106+
107+
## Differences from /auto-resolve-loop
108+
109+
| Feature | /auto-resolve | /auto-resolve-loop |
110+
|---------|---------------|-------------------|
111+
| Mode | One-shot | Continuous |
112+
| Stops after | N issues | Never (until interrupted) |
113+
| Best for | Quick fixes | Maintenance sprints |
114+
| Token usage | Fixed (N issues) | Unbounded |
115+
| User control | High | Low |
116+
117+
## When to Use
118+
119+
**Use /auto-resolve when:**
120+
- You have 5-20 issues to resolve
121+
- You want to review progress between batches
122+
- You want predictable token usage
123+
- You're testing the autonomous workflow
124+
125+
**Use /auto-resolve-loop when:**
126+
- You have a large backlog (50+ issues)
127+
- You want continuous work while you're away
128+
- You trust the quality gates completely
129+
- You have a comprehensive test suite
130+
131+
## Prerequisites
132+
133+
Your project MUST have:
134+
- ✅ Comprehensive test suite
135+
- ✅ Automated code formatting
136+
- ✅ Linting/static analysis
137+
- ✅ Well-defined GitHub issues
138+
- ✅ GitHub CLI configured (`gh auth login`)
139+
140+
## See Also
141+
142+
- `/auto-resolve-loop` - Continuous issue resolution
143+
- `/auto-review` - One-shot code review
144+
- `/auto-review-loop` - Continuous code review
145+
- [AUTO_RESOLVE_MODE.md](../../AUTO_RESOLVE_MODE.md) - Full documentation

‎.claude/skills/auto-review-loop.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: auto-review-loop
3+
description: Continuously review code on a schedule (daily/weekly)
4+
---
5+
6+
# Auto-Review Loop Skill
7+
8+
Continuously monitor code quality with scheduled reviews.
9+
10+
## What This Skill Does
11+
12+
Runs code reviews on a schedule (daily, weekly, etc.) and creates issues for findings.
13+
14+
## See Also
15+
16+
- `/auto-review` - One-shot code review
17+
- [CONTINUOUS_REVIEW_GUIDE.md](../../CONTINUOUS_REVIEW_GUIDE.md) - Full documentation

0 commit comments

Comments
 (0)