claude-code-autoconfig 1.0.20 → 1.0.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# Subagents
|
|
2
|
+
|
|
3
|
+
Define autonomous background workers here. Each .md file becomes a subagent Claude can spawn.
|
|
4
|
+
|
|
5
|
+
<!-- ╔══════════════════════════════════════════════════════════════════╗
|
|
6
|
+
║ ║
|
|
7
|
+
║ TEMPLATE BELOW — DELETE THIS BLOCK WHEN ADDING REAL AGENTS ║
|
|
8
|
+
║ ║
|
|
9
|
+
╠══════════════════════════════════════════════════════════════════╣
|
|
10
|
+
║ ║
|
|
11
|
+
║ ## agent-name.md ║
|
|
12
|
+
║ ║
|
|
13
|
+
║ <!-- Brief description for guide hover --> ║
|
|
14
|
+
║ ║
|
|
15
|
+
║ # Agent Name ║
|
|
16
|
+
║ ║
|
|
17
|
+
║ Describe what this agent does, when it runs, ║
|
|
18
|
+
║ and what it has access to. ║
|
|
19
|
+
║ ║
|
|
20
|
+
║ ## Trigger ║
|
|
21
|
+
║ - Via hook (PostToolUse, Stop, etc.) ║
|
|
22
|
+
║ - Via slash command ║
|
|
23
|
+
║ - Via another agent ║
|
|
24
|
+
║ ║
|
|
25
|
+
║ ## Scope ║
|
|
26
|
+
║ What files/directories can this agent access? ║
|
|
27
|
+
║ What actions can it take? ║
|
|
28
|
+
║ ║
|
|
29
|
+
╚══════════════════════════════════════════════════════════════════╝ -->
|
|
@@ -0,0 +1,62 @@
|
|
|
1
|
+
<!-- @description Creates a formatted retro item when tech debt or improvements are spotted. -->
|
|
2
|
+
|
|
3
|
+
# Create Retro Item Agent
|
|
4
|
+
|
|
5
|
+
Create a fully-scoped story file in `.claude/retro/` when tech debt or improvement opportunities are identified.
|
|
6
|
+
|
|
7
|
+
## When to Trigger
|
|
8
|
+
|
|
9
|
+
Call this agent when you notice:
|
|
10
|
+
- Tech debt that should be addressed later
|
|
11
|
+
- Code that works but could be improved
|
|
12
|
+
- Missing tests, documentation, or error handling
|
|
13
|
+
- Architectural improvements worth tracking
|
|
14
|
+
|
|
15
|
+
## Input
|
|
16
|
+
|
|
17
|
+
Provide these details when calling:
|
|
18
|
+
- **title**: Short descriptive name (used for filename)
|
|
19
|
+
- **problem**: What's wrong or what friction was encountered
|
|
20
|
+
- **criteria**: Specific, testable acceptance criteria
|
|
21
|
+
- **approach**: How to fix it
|
|
22
|
+
- **priority**: Critical | High | Medium | Low
|
|
23
|
+
- **effort**: S | M | L | XL
|
|
24
|
+
- **files**: List of files involved
|
|
25
|
+
|
|
26
|
+
## Behavior
|
|
27
|
+
|
|
28
|
+
1. Generate filename from title: `kebab-case.md`
|
|
29
|
+
2. Create story file in `.claude/retro/` using this format:
|
|
30
|
+
|
|
31
|
+
```markdown
|
|
32
|
+
# [Title]
|
|
33
|
+
|
|
34
|
+
## Problem
|
|
35
|
+
[Problem description]
|
|
36
|
+
|
|
37
|
+
## Acceptance Criteria
|
|
38
|
+
- [ ] [Criteria 1]
|
|
39
|
+
- [ ] [Criteria 2]
|
|
40
|
+
|
|
41
|
+
## Approach
|
|
42
|
+
[How to fix]
|
|
43
|
+
|
|
44
|
+
## Priority
|
|
45
|
+
[Priority level]
|
|
46
|
+
|
|
47
|
+
## Effort
|
|
48
|
+
[Effort size]
|
|
49
|
+
|
|
50
|
+
## Files
|
|
51
|
+
- [file1]
|
|
52
|
+
- [file2]
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
3. Confirm creation with filename
|
|
56
|
+
|
|
57
|
+
## Guidelines
|
|
58
|
+
|
|
59
|
+
- **Be concise**: Keep descriptions actionable, not verbose
|
|
60
|
+
- **Be specific**: Include actual file paths and line numbers when relevant
|
|
61
|
+
- **Don't duplicate**: Check if similar item already exists first
|
|
62
|
+
- **Don't block**: Create the item and continue with the main task
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
<!-- @description Background worker that syncs the guide when .claude/ files change. -->
|
|
2
|
+
|
|
3
|
+
# Guide Refresh Agent
|
|
4
|
+
|
|
5
|
+
Incrementally update the guide's treeInfo when `.claude/` files are added or modified.
|
|
6
|
+
|
|
7
|
+
## Trigger
|
|
8
|
+
|
|
9
|
+
- PostToolUse hook on Edit|Write to `.claude/`
|
|
10
|
+
|
|
11
|
+
## Scope
|
|
12
|
+
|
|
13
|
+
- Read `.claude/**/*.md` for `@description` comments
|
|
14
|
+
- Update `.claude/guide/autoconfig.guide.html` treeInfo
|
|
15
|
+
|
|
16
|
+
## Behavior
|
|
17
|
+
|
|
18
|
+
1. Check which `.claude/` file was just modified
|
|
19
|
+
2. Extract the `<!-- @description ... -->` comment from the top
|
|
20
|
+
3. Find the corresponding entry in the guide's `treeInfo` object
|
|
21
|
+
4. Update only that entry's `desc` field
|
|
22
|
+
5. If file is new, add a new treeInfo entry
|
|
23
|
+
6. If file was deleted, remove the treeInfo entry
|
|
24
|
+
|
|
25
|
+
## Guidelines
|
|
26
|
+
|
|
27
|
+
- **Be fast**: Only touch the affected entry
|
|
28
|
+
- **Be minimal**: Don't reformat or reorganize unrelated code
|
|
29
|
+
- **Be silent**: Run in background, no output unless error
|
|
@@ -181,7 +181,7 @@ del nul 2>nul
|
|
|
181
181
|
|
|
182
182
|
This is safe to run even if the file doesn't exist.
|
|
183
183
|
|
|
184
|
-
### Open Guide
|
|
184
|
+
### Open Guide & Finale
|
|
185
185
|
|
|
186
186
|
Open the interactive guide in the user's browser:
|
|
187
187
|
|
|
@@ -189,4 +189,12 @@ Open the interactive guide in the user's browser:
|
|
|
189
189
|
- Linux: `xdg-open .claude/guide/autoconfig.guide.html`
|
|
190
190
|
- Windows: `start .claude/guide/autoconfig.guide.html`
|
|
191
191
|
|
|
192
|
-
|
|
192
|
+
Then output a celebratory finale message:
|
|
193
|
+
|
|
194
|
+
```
|
|
195
|
+
---
|
|
196
|
+
|
|
197
|
+
✅ Setup complete! Your Claude Code environment is ready.
|
|
198
|
+
|
|
199
|
+
📖 The interactive guide is now open — it walks through everything that was configured.
|
|
200
|
+
```
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claude-code-autoconfig",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.22",
|
|
4
4
|
"description": "Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.",
|
|
5
5
|
"author": "ADAC 1001 <info@adac1001.com>",
|
|
6
6
|
"license": "MIT",
|