oh-my-customcode 0.44.6 → 0.45.1
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.
- package/README.md +5 -5
- package/dist/cli/index.js +12866 -92
- package/package.json +2 -1
- package/templates/.claude/skills/ambiguity-gate/SKILL.md +94 -0
- package/templates/.claude/skills/omcustom-feedback/SKILL.md +137 -0
- package/templates/.claude/skills/sdd/SKILL.md +24 -0
- package/templates/.claude/skills/sdd-dev/SKILL.md +257 -0
- package/templates/.claude/skills/sdd-development/SKILL.md +24 -0
- package/templates/CLAUDE.md +4 -2
- package/templates/guides/git-worktree-workflow/README.md +134 -0
- package/templates/guides/skill-bundle-design/README.md +106 -0
- package/templates/manifest.json +3 -3
|
@@ -0,0 +1,134 @@
|
|
|
1
|
+
# Git Worktree Workflow
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
Git worktrees allow you to check out multiple branches simultaneously in separate directories, each with its own working tree. This eliminates the need to stash changes or commit incomplete work when switching between branches.
|
|
6
|
+
|
|
7
|
+
**Key benefits:**
|
|
8
|
+
- Work on `develop` and `team-plugin` simultaneously without context switching
|
|
9
|
+
- Keep long-running feature branches open alongside hotfix branches
|
|
10
|
+
- Run tests on one branch while coding on another
|
|
11
|
+
|
|
12
|
+
## Recommended Directory Structure
|
|
13
|
+
|
|
14
|
+
```
|
|
15
|
+
~/workspace/projects/
|
|
16
|
+
├── oh-my-customcode/ # Main worktree (develop)
|
|
17
|
+
├── oh-my-customcode-team-plugin/ # team-plugin branch
|
|
18
|
+
└── oh-my-customcode-release/ # release/* branches
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Convention: `{repo-name}-{branch-suffix}` as sibling directories to the main worktree.
|
|
22
|
+
|
|
23
|
+
## Basic Commands
|
|
24
|
+
|
|
25
|
+
### Create a worktree
|
|
26
|
+
|
|
27
|
+
```bash
|
|
28
|
+
# From the main repository directory
|
|
29
|
+
cd ~/workspace/projects/oh-my-customcode
|
|
30
|
+
|
|
31
|
+
# Attach to an existing remote branch
|
|
32
|
+
git worktree add ../oh-my-customcode-team-plugin team-plugin
|
|
33
|
+
|
|
34
|
+
# Create a new branch and worktree together
|
|
35
|
+
git worktree add ../oh-my-customcode-release release/v0.43.0
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
### List worktrees
|
|
39
|
+
|
|
40
|
+
```bash
|
|
41
|
+
git worktree list
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
Output:
|
|
45
|
+
```
|
|
46
|
+
/Users/you/workspace/projects/oh-my-customcode abc1234 [develop]
|
|
47
|
+
/Users/you/workspace/projects/oh-my-customcode-team-plugin def5678 [team-plugin]
|
|
48
|
+
/Users/you/workspace/projects/oh-my-customcode-release ghi9012 [release/v0.43.0]
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
### Remove a worktree
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
# Remove after branch is merged
|
|
55
|
+
git worktree remove ../oh-my-customcode-release
|
|
56
|
+
|
|
57
|
+
# Clean up stale worktree references
|
|
58
|
+
git worktree prune
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
### Move a worktree
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
git worktree move ../oh-my-customcode-release ../oh-my-customcode-hotfix
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
## Claude Code Integration
|
|
68
|
+
|
|
69
|
+
### Built-in Worktree Tools
|
|
70
|
+
|
|
71
|
+
Claude Code provides `EnterWorktree` and `ExitWorktree` tools for session-scoped worktree management:
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
EnterWorktree(name: "feature-x")
|
|
75
|
+
# Creates .claude/worktrees/feature-x with a new branch based on HEAD
|
|
76
|
+
# Session working directory switches to the worktree
|
|
77
|
+
|
|
78
|
+
ExitWorktree()
|
|
79
|
+
# Returns to the main repository
|
|
80
|
+
# Prompts to keep or remove the worktree
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
### Agent Isolation Mode
|
|
84
|
+
|
|
85
|
+
Agents can use `isolation: worktree` in their frontmatter to run in an isolated git worktree:
|
|
86
|
+
|
|
87
|
+
```yaml
|
|
88
|
+
---
|
|
89
|
+
name: my-agent
|
|
90
|
+
isolation: worktree
|
|
91
|
+
---
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
This gives the agent a separate working copy, enabling safe code changes with rollback capability. The worktree is automatically created and cleaned up by the agent lifecycle.
|
|
95
|
+
|
|
96
|
+
### Superpowers Skill
|
|
97
|
+
|
|
98
|
+
The `superpowers` plugin includes a `using-git-worktrees` skill with additional patterns for worktree-based workflows. Reference it for advanced use cases like parallel CI testing and multi-branch refactoring.
|
|
99
|
+
|
|
100
|
+
## Caveats
|
|
101
|
+
|
|
102
|
+
### Same branch restriction
|
|
103
|
+
|
|
104
|
+
A branch cannot be checked out in multiple worktrees simultaneously. Attempting this will fail:
|
|
105
|
+
|
|
106
|
+
```bash
|
|
107
|
+
# ERROR: 'develop' is already checked out at '~/workspace/projects/oh-my-customcode'
|
|
108
|
+
git worktree add ../oh-my-customcode-dev2 develop
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
### Independent dependencies
|
|
112
|
+
|
|
113
|
+
Each worktree has its own `node_modules`. Run package installation separately:
|
|
114
|
+
|
|
115
|
+
```bash
|
|
116
|
+
cd ../oh-my-customcode-team-plugin
|
|
117
|
+
bun install
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
### Gitignored files
|
|
121
|
+
|
|
122
|
+
Files under `.claude/` are gitignored in this project. When adding new `.claude/` files, use `git add -f`:
|
|
123
|
+
|
|
124
|
+
```bash
|
|
125
|
+
git add -f .claude/agents/new-agent.md
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
### Shared git objects
|
|
129
|
+
|
|
130
|
+
All worktrees share the same `.git` object store. Operations like `git gc` and `git fetch` affect all worktrees.
|
|
131
|
+
|
|
132
|
+
### Worktree-local files
|
|
133
|
+
|
|
134
|
+
Files listed in `.gitignore` (like `node_modules/`, `.env`) are independent per worktree. Configuration files that are not tracked must be set up separately in each worktree.
|
|
@@ -0,0 +1,106 @@
|
|
|
1
|
+
# Domain Skill Bundle Design Guide
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
Domain skill bundles package related skills, agents, and guides for a specific technology or framework. This guide defines the standard pattern based on the Author/Test/Troubleshoot tri-pattern (inspired by Microsoft Copilot Studio Skills).
|
|
6
|
+
|
|
7
|
+
## The Author/Test/Troubleshoot Pattern
|
|
8
|
+
|
|
9
|
+
Every domain skill bundle should provide three capability axes:
|
|
10
|
+
|
|
11
|
+
### Author (Create & Edit)
|
|
12
|
+
Skills and agents that help CREATE artifacts in the domain.
|
|
13
|
+
|
|
14
|
+
| Component | Example (Spring Boot) | Example (Airflow) |
|
|
15
|
+
|-----------|----------------------|-------------------|
|
|
16
|
+
| Best practices skill | springboot-best-practices | airflow-best-practices |
|
|
17
|
+
| Expert agent | be-springboot-expert | de-airflow-expert |
|
|
18
|
+
| Code generation | Scaffold, boilerplate | DAG authoring |
|
|
19
|
+
|
|
20
|
+
### Test (Verify & Validate)
|
|
21
|
+
Skills and agents that help VERIFY correctness.
|
|
22
|
+
|
|
23
|
+
| Component | Example (Spring Boot) | Example (Airflow) |
|
|
24
|
+
|-----------|----------------------|-------------------|
|
|
25
|
+
| Review skill | dev-review | dev-review |
|
|
26
|
+
| QA workflow | qa-lead-routing | qa-lead-routing |
|
|
27
|
+
| Domain-specific checks | Spring actuator health | DAG validation |
|
|
28
|
+
|
|
29
|
+
### Troubleshoot (Debug & Fix)
|
|
30
|
+
Skills and agents that help DIAGNOSE and FIX issues.
|
|
31
|
+
|
|
32
|
+
| Component | Example (Spring Boot) | Example (Airflow) |
|
|
33
|
+
|-----------|----------------------|-------------------|
|
|
34
|
+
| Debugging skill | systematic-debugging | systematic-debugging |
|
|
35
|
+
| Domain diagnostics | Spring Boot Actuator | Airflow log analysis |
|
|
36
|
+
| Fix patterns | Common Spring errors | DAG failure patterns |
|
|
37
|
+
|
|
38
|
+
## Existing Bundle Inventory
|
|
39
|
+
|
|
40
|
+
Map existing oh-my-customcode skills/agents to the tri-pattern:
|
|
41
|
+
|
|
42
|
+
| Domain | Author | Test | Troubleshoot | Completeness |
|
|
43
|
+
|--------|--------|------|-------------|-------------|
|
|
44
|
+
| Spring Boot | springboot-best-practices, be-springboot-expert | dev-review | systematic-debugging | ★★★ |
|
|
45
|
+
| FastAPI | fastapi-best-practices, be-fastapi-expert | dev-review | systematic-debugging | ★★★ |
|
|
46
|
+
| Go | go-best-practices, lang-golang-expert, be-go-backend-expert | dev-review | systematic-debugging | ★★★ |
|
|
47
|
+
| Airflow | airflow-best-practices, de-airflow-expert | dev-review | systematic-debugging | ★★★ |
|
|
48
|
+
| React/Next.js | react-best-practices, fe-vercel-agent | web-design-guidelines | systematic-debugging | ★★★ |
|
|
49
|
+
| PostgreSQL | postgres-best-practices, db-postgres-expert | dev-review | systematic-debugging | ★★★ |
|
|
50
|
+
| Docker | docker-best-practices, infra-docker-expert | dev-review | systematic-debugging | ★★☆ |
|
|
51
|
+
| Kafka | kafka-best-practices, de-kafka-expert | dev-review | systematic-debugging | ★★☆ |
|
|
52
|
+
| Redis | redis-best-practices, db-redis-expert | dev-review | systematic-debugging | ★★☆ |
|
|
53
|
+
|
|
54
|
+
## Creating a New Bundle
|
|
55
|
+
|
|
56
|
+
### Checklist
|
|
57
|
+
|
|
58
|
+
1. **Author axis**:
|
|
59
|
+
- [ ] Best practices skill (`.claude/skills/{domain}-best-practices/SKILL.md`)
|
|
60
|
+
- [ ] Expert agent (`.claude/agents/{type}-{domain}-expert.md`)
|
|
61
|
+
- [ ] Reference guide (`guides/{domain}/`)
|
|
62
|
+
|
|
63
|
+
2. **Test axis**:
|
|
64
|
+
- [ ] Domain-specific test patterns documented in best practices skill
|
|
65
|
+
- [ ] Integration with qa-lead-routing or dev-review
|
|
66
|
+
|
|
67
|
+
3. **Troubleshoot axis**:
|
|
68
|
+
- [ ] Common error patterns documented in best practices skill
|
|
69
|
+
- [ ] Integration with systematic-debugging
|
|
70
|
+
|
|
71
|
+
### Minimum Viable Bundle
|
|
72
|
+
|
|
73
|
+
At minimum, a domain bundle needs:
|
|
74
|
+
- 1 best practices skill (Author)
|
|
75
|
+
- 1 expert agent (Author + Troubleshoot)
|
|
76
|
+
- Integration with dev-review (Test)
|
|
77
|
+
|
|
78
|
+
### Template
|
|
79
|
+
|
|
80
|
+
```
|
|
81
|
+
guides/{domain}/
|
|
82
|
+
├── README.md # Domain overview and quick reference
|
|
83
|
+
├── patterns.md # Common patterns and anti-patterns
|
|
84
|
+
└── troubleshooting.md # Common errors and solutions
|
|
85
|
+
|
|
86
|
+
.claude/skills/{domain}-best-practices/
|
|
87
|
+
└── SKILL.md # Best practices skill
|
|
88
|
+
|
|
89
|
+
.claude/agents/{type}-{domain}-expert.md # Expert agent
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
## Relationship to Other Skills
|
|
93
|
+
|
|
94
|
+
| Skill | Role in Bundle Pattern |
|
|
95
|
+
|-------|----------------------|
|
|
96
|
+
| dev-review | Universal Test axis |
|
|
97
|
+
| systematic-debugging | Universal Troubleshoot axis |
|
|
98
|
+
| adversarial-review | Advanced Test axis (security) |
|
|
99
|
+
| qa-lead-routing | Test orchestration |
|
|
100
|
+
| mgr-creator | Bundle creation automation |
|
|
101
|
+
|
|
102
|
+
## References
|
|
103
|
+
|
|
104
|
+
- Microsoft Copilot Studio Skills: Author/Test/Troubleshoot pattern
|
|
105
|
+
- oh-my-customcode R006: Agent Design (separation of concerns)
|
|
106
|
+
- oh-my-customcode compilation metaphor: skills = source, agents = build artifacts
|
package/templates/manifest.json
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "0.
|
|
2
|
+
"version": "0.45.1",
|
|
3
3
|
"lastUpdated": "2026-03-16T00:00:00.000Z",
|
|
4
4
|
"components": [
|
|
5
5
|
{
|
|
@@ -18,13 +18,13 @@
|
|
|
18
18
|
"name": "skills",
|
|
19
19
|
"path": ".claude/skills",
|
|
20
20
|
"description": "Reusable skill modules (includes slash commands)",
|
|
21
|
-
"files":
|
|
21
|
+
"files": 82
|
|
22
22
|
},
|
|
23
23
|
{
|
|
24
24
|
"name": "guides",
|
|
25
25
|
"path": "guides",
|
|
26
26
|
"description": "Reference documentation",
|
|
27
|
-
"files":
|
|
27
|
+
"files": 28
|
|
28
28
|
},
|
|
29
29
|
{
|
|
30
30
|
"name": "hooks",
|