@ravshansbox/pi-next-issue 2.5.9 → 2.6.0

package/README.md

@@ -16,6 +16,17 @@ Run this in pi, inside a git repository:
 
 The footer shows the issue, the stage, the number of tool calls and the time spent on the issue, for example `next-issue #12 · review 1 · 37 tools · 4m12s`. After a run ends, it keeps the last summary. In the terminal, it uses the dim colour of the theme, like the rest of the footer. A note appears when an issue is done, needs a human or fails while pi is open. Pi does not repeat the notes of a run that ended before it opened.
 
+## Create an issue
+
+The package ships the `create-issue` skill. Ask pi to write an issue, or run `/skill:create-issue <problem>`. Pi then:
+
+1. restates the problem and reads the code when the problem touches it;
+2. asks numbered questions until none is open;
+3. shows the title and the body, and waits for you to confirm;
+4. runs `gh issue create --body-file` with the body from [`template.md`](skills/create-issue/template.md) and the `status:todo` label.
+
+Pi does not implement the issue in that session. The worker does the work. The body holds the sections of the [issue format](../next-issue/README.md#issue-format).
+
 ## Worker
 
 The extension does no work itself. On `/next-issue` it connects to the `next-issue` worker on the socket file `~/.pi/agent/next-issue.sock`. When no worker answers, it starts one with `npx -y next-issue@<version> serve`, where `<version>` is the version of the extension, or `latest` when the extension runs from a source checkout with version `0.0.0`, in the background, and writes the output of the worker to `~/.pi/agent/next-issue-worker.log`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ravshansbox/pi-next-issue",
-  "version": "2.5.9",
+  "version": "2.6.0",
   "description": "Pi extension that works through GitHub issues with the next-issue worker",
   "license": "MIT",
   "type": "module",
@@ -16,12 +16,16 @@
   "keywords": [
     "pi-package",
     "pi-extension",
+    "pi-skill",
     "github",
     "issues"
   ],
   "pi": {
     "extensions": [
       "./index.ts"
+    ],
+    "skills": [
+      "./skills"
     ]
   },
   "scripts": {
@@ -45,7 +49,8 @@
   },
   "files": [
     "index.ts",
-    "src"
+    "src",
+    "skills"
   ],
   "publishConfig": {
     "access": "public"

package/skills/create-issue/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: create-issue
+description: Turn a problem into a clear GitHub issue that the next-issue worker can claim. Use when the user wants to write, file or create an issue.
+---
+
+# Create an issue
+
+Turn the problem of the user into one GitHub issue in the format of `template.md`, next to this file.
+
+1. Understand the problem. Restate it in your own words.
+2. Investigate the code when the problem touches it. Read the relevant files and note what you find, with file paths.
+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.
+4. Write the body from `template.md` into a temporary file. Keep every heading of the template and its order. Leave `Open questions` empty.
+5. Show the title and the body to the user, and ask for confirmation. Change the draft and show it again until the user confirms.
+6. Only after the user confirms, create the issue:
+
+   ```bash
+   gh issue create --title "<title>" --body-file <file> --label status:todo
+   ```
+
+7. Tell the user the issue url.
+
+Once the issue exists, do not implement it in this session. The next-issue worker does the work.
+
+## Sections
+
+- Problem: what is wrong or missing, and who it affects.
+- Context and findings: what you found in the code and the docs, with paths.
+- Acceptance criteria: a list of checks that show the issue is done, each one observable.
+- Out of scope: what the issue does not cover.
+- Open questions: empty when the issue is created.

package/skills/create-issue/template.md

@@ -0,0 +1,9 @@
+## Problem
+
+## Context and findings
+
+## Acceptance criteria
+
+## Out of scope
+
+## Open questions