@ravshansbox/pi-next-issue 5.6.2 → 5.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/README.md +1 -1
- package/package.json +1 -1
- package/skills/create-issue/SKILL.md +8 -1
package/README.md
CHANGED
|
@@ -36,7 +36,7 @@ The package ships the `create-issue` skill. Ask pi to write an issue, ask for a
|
|
|
36
36
|
|
|
37
37
|
1. restates the problem, reads the code when the problem touches it, and finds the open issues that must be done first;
|
|
38
38
|
2. asks numbered questions until none is open;
|
|
39
|
-
3. runs `gh issue create --body-file` with the body from [`template.md`](skills/create-issue/template.md) and the `status:todo` label, without showing the body first;
|
|
39
|
+
3. creates the `status:todo` label with `gh label create` when the repository does not have it, then runs `gh issue create --body-file` with the body from [`template.md`](skills/create-issue/template.md) and the `status:todo` label, without showing the body first;
|
|
40
40
|
4. links each blocker with `gh issue edit --add-blocked-by`, so the worker waits for it;
|
|
41
41
|
5. gives you the issue url and asks once whether to start a run, leave it or change it, and changes it with `gh issue edit --body-file` or `--title` until you start a run or leave it;
|
|
42
42
|
6. calls `next_issue_start` when you asked for a run.
|
package/package.json
CHANGED
|
@@ -11,7 +11,14 @@ Turn the problem of the user into one GitHub issue in the format of `template.md
|
|
|
11
11
|
2. Investigate the code when the problem touches it. Read the relevant files and note what you find, with file paths. Run `gh issue list` and note each open issue that must be done first, including the issues you create in the same session.
|
|
12
12
|
3. Ask numbered questions about anything that is unclear: the scope, the expected behaviour, the acceptance criteria. Label options with letters and recommend one. Ask again until no question is open.
|
|
13
13
|
4. Write the body from `template.md` into a temporary file. Keep every heading of the template and its order. Leave `Open questions` empty.
|
|
14
|
-
5. Create the
|
|
14
|
+
5. Create the `status:todo` label when the repository does not have it, so the worker can claim the issue:
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
gh label list --search status:todo
|
|
18
|
+
gh label create status:todo
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Then create the issue without showing the body first:
|
|
15
22
|
|
|
16
23
|
```bash
|
|
17
24
|
gh issue create --title "<title>" --body-file <file> --label status:todo
|