@sven1103/opencode-worktree-workflow 0.6.2 → 0.6.3
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: worktree-workflow
|
|
3
|
-
description: Use this skill when
|
|
3
|
+
description: Use this skill when working on changes that should be isolated from the main repo, such as refactoring multiple files, making risky edits, experimenting, creating parallel work (like branches or worktrees), or when you are unsure whether it is safe to edit directly in the repo root. Use it when you are orchestrating tasks for implementation and review. Not needed for small, simple one-file edits.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
## When to use me
|
|
@@ -49,6 +49,27 @@ description: Use this skill when you need to decide whether a task should move i
|
|
|
49
49
|
- Use cleanup apply only when deletion is clearly intended and controlled by the orchestrating runtime.
|
|
50
50
|
- Treat slash commands as manual human entry points, not as the canonical agent interface.
|
|
51
51
|
|
|
52
|
+
## Result reporting
|
|
53
|
+
|
|
54
|
+
- Always surface the concrete outcome of worktree operations to the user.
|
|
55
|
+
- Do not summarize away important details.
|
|
56
|
+
|
|
57
|
+
When a worktree is created, include:
|
|
58
|
+
- The worktree path
|
|
59
|
+
- The branch name (if created or used)
|
|
60
|
+
- The base branch
|
|
61
|
+
- Whether it was newly created or reused
|
|
62
|
+
|
|
63
|
+
When cleanup is run:
|
|
64
|
+
- Show the preview or the list of affected worktrees
|
|
65
|
+
- Clearly distinguish preview vs applied changes
|
|
66
|
+
|
|
67
|
+
When commands are executed inside a worktree:
|
|
68
|
+
- Mention that the worktree path is the active working directory
|
|
69
|
+
- Include relevant command results (status, diff summary, errors)
|
|
70
|
+
|
|
71
|
+
Prefer structured, explicit output over vague summaries.
|
|
72
|
+
|
|
52
73
|
## Boundaries
|
|
53
74
|
|
|
54
75
|
- Do not encode runtime storage, session artifact, or orchestration file-layout details here.
|