claude-plugin-viban 1.3.5 → 1.3.7
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/.claude-plugin/plugin.json +1 -1
- package/package.json +1 -1
- package/skills/assign/SKILL.md +61 -25
package/package.json
CHANGED
package/skills/assign/SKILL.md
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: assign
|
|
3
|
-
description: "Assign first backlog issue
|
|
3
|
+
description: "Assign first backlog issue and resolve it through to review"
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# /assign
|
|
7
7
|
|
|
8
|
-
Assign the first backlog issue. If the description is unclear
|
|
8
|
+
Assign the first backlog issue and execute the full resolution workflow. If the description is unclear, interview the user first.
|
|
9
9
|
|
|
10
10
|
> **CLI only** (no direct viban.json access)
|
|
11
11
|
|
|
@@ -24,7 +24,7 @@ done
|
|
|
24
24
|
```
|
|
25
25
|
Look for `Issue Resolution Workflow` or `Workflow` section.
|
|
26
26
|
|
|
27
|
-
If a workflow exists, follow its conventions
|
|
27
|
+
If a workflow exists, **follow it exactly** — its pipeline, conventions, and stop points override the defaults below.
|
|
28
28
|
|
|
29
29
|
---
|
|
30
30
|
|
|
@@ -47,24 +47,11 @@ Display the issue title, description, priority, and type to the user.
|
|
|
47
47
|
|
|
48
48
|
## Step 3: Evaluate Clarity
|
|
49
49
|
|
|
50
|
-
Assess whether the issue description provides enough context
|
|
50
|
+
Assess whether the issue description provides enough context to start working:
|
|
51
51
|
|
|
52
52
|
- **Clear**: the symptom, affected area, and expected behavior are all understandable
|
|
53
53
|
- **Unclear**: vague description, missing context, ambiguous scope, or multiple possible interpretations
|
|
54
54
|
|
|
55
|
-
### If Clear
|
|
56
|
-
|
|
57
|
-
Report the assignment and finish:
|
|
58
|
-
|
|
59
|
-
```
|
|
60
|
-
Issue #{id} assigned
|
|
61
|
-
Title: {title}
|
|
62
|
-
Priority: {priority} | Type: {type}
|
|
63
|
-
Status: in_progress
|
|
64
|
-
|
|
65
|
-
Ready for work.
|
|
66
|
-
```
|
|
67
|
-
|
|
68
55
|
### If Unclear
|
|
69
56
|
|
|
70
57
|
Interview the user with AskUserQuestion to gather missing context. Ask about:
|
|
@@ -86,24 +73,73 @@ VIBAN_EOF
|
|
|
86
73
|
# Re-add the issue with enriched description (edit via TUI or recreate)
|
|
87
74
|
```
|
|
88
75
|
|
|
89
|
-
|
|
76
|
+
## Step 4: Execute Workflow
|
|
77
|
+
|
|
78
|
+
Follow the workflow from Step 0. If no workflow was found, use this default pipeline:
|
|
79
|
+
|
|
80
|
+
### 4.1 Analyze
|
|
81
|
+
- Explore the codebase to understand the issue
|
|
82
|
+
- Identify root cause and scope of change
|
|
83
|
+
|
|
84
|
+
### 4.2 Implement
|
|
85
|
+
- Create a branch: `git checkout -b issue-{ISSUE_ID}`
|
|
86
|
+
- Make the fix/feature changes
|
|
87
|
+
- Write or update tests as appropriate
|
|
88
|
+
|
|
89
|
+
### 4.3 Verify
|
|
90
|
+
- Run build and tests to confirm the fix works
|
|
91
|
+
- Verify no regressions
|
|
92
|
+
|
|
93
|
+
### 4.4 Ship (MANDATORY)
|
|
94
|
+
|
|
95
|
+
Every step below is **required** unless the workflow explicitly says to stop earlier.
|
|
96
|
+
|
|
97
|
+
```bash
|
|
98
|
+
# 1. Commit
|
|
99
|
+
git add -A
|
|
100
|
+
git commit -m "fix: {description} (#$ISSUE_ID)"
|
|
90
101
|
|
|
102
|
+
# 2. Push
|
|
103
|
+
git push -u origin issue-$ISSUE_ID
|
|
104
|
+
|
|
105
|
+
# 3. Create PR (REQUIRED — do NOT skip this)
|
|
106
|
+
gh pr create --title "fix: {description}" --body "Resolves #$ISSUE_ID
|
|
107
|
+
|
|
108
|
+
## Summary
|
|
109
|
+
{what was changed and why}
|
|
110
|
+
|
|
111
|
+
## Test plan
|
|
112
|
+
{how it was verified}"
|
|
91
113
|
```
|
|
92
|
-
Issue #{id} assigned and clarified
|
|
93
|
-
Title: {title}
|
|
94
|
-
Priority: {priority} | Type: {type}
|
|
95
|
-
Status: in_progress
|
|
96
114
|
|
|
97
|
-
|
|
115
|
+
**If `gh pr create` fails**: fix the error and retry. Do NOT skip PR creation.
|
|
116
|
+
|
|
117
|
+
## Step 5: Move to Review
|
|
118
|
+
|
|
119
|
+
After PR is created:
|
|
120
|
+
|
|
121
|
+
```bash
|
|
122
|
+
viban review $ISSUE_ID
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
Report completion with the PR URL:
|
|
126
|
+
|
|
98
127
|
```
|
|
128
|
+
Issue #{id} resolved → review
|
|
129
|
+
Title: {title}
|
|
130
|
+
PR: {pr_url}
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
**Do NOT report completion without a PR URL.**
|
|
99
134
|
|
|
100
135
|
---
|
|
101
136
|
|
|
102
137
|
## CRITICAL
|
|
103
138
|
|
|
104
139
|
> - **NEVER read or write `viban.json` directly** — always use `viban` CLI commands (`viban assign`, `viban get`, `viban list`, `viban done`, etc.)
|
|
105
|
-
> -
|
|
106
|
-
> -
|
|
140
|
+
> - **MUST create a PR** via `gh pr create` unless the workflow explicitly says "stop before PR".
|
|
141
|
+
> - **MUST call `viban review`** after PR creation. Do NOT finish without moving the issue to review.
|
|
142
|
+
> - **MUST include PR URL** in the completion report. No URL = not done.
|
|
107
143
|
|
|
108
144
|
## CLI Reference
|
|
109
145
|
|