@ravshansbox/pi-next-issue 2.17.0 → 2.19.0

package/README.md

@@ -14,9 +14,9 @@ Run this in pi, inside a git repository:
 
 - `/next-issue` starts a run of this repository when none is going, and stops the run when one is going. A stop takes effect after the current round, and the issue keeps its saved state, so the next run resumes it.
 - The `next_issue_start` tool lets the model start a run. When no run is going, it starts a run like `/next-issue`. When a run is going, it starts nothing and reports the current run, which picks up new issues by itself. It never stops a run, and it does not ask for confirmation. Its result says whether it started a run.
-- The `next_issue_status` tool lets the model see the run of this repository. It returns the footer line, then one line per handled issue with its outcome, for example `#190 done`. When the worker has no run of this repository, it returns `next-issue · no run of <root>`. When no worker is going, it returns `next-issue · no worker is running` and does not start one. It reports no other repository.
+- The `next_issue_status` tool lets the model see the run of this repository. It returns the footer line, then one line per handled issue with its outcome, for example `#190 done`. When the worker has no run of this repository, it returns `no run of <root>`. When no worker is going, it returns `no worker is running` and does not start one. It reports no other repository.
 
-The footer shows each running issue with its stage, the number of tool calls and the time spent on it, for example `next-issue #12 · review 1 · 37 tools · 4m12s | #13 · implement · 5 tools · 40s`. 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.
+The footer shows each running issue with the number of open issues at the latest fetch, its stage, the number of tool calls and the time spent on it, for example `#12/7 · review 2/5 · 37 tools · 4m12s | #13/7 · implement · 5 tools · 40s`. The open count includes the running issues and issues the run skips. A stage with a limited number of rounds shows the round and its limit: `review 2/5`, `review fix 2/5`, `checks fix 1/5` or `commit fix 1/10`. Other lines read, for example, `looking for issues`, `finished: 2 done` or `stopped: 1 done, 1 needs a human`. 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.
 
 ## Answer questions
 
@@ -32,7 +32,7 @@ Press Escape, or leave the guidance empty, to stop. Pi reads the list again befo
 
 ## Create an issue
 
-The package ships the `create-issue` skill. Ask pi to write an issue, or run `/skill:create-issue <problem>`. Pi then:
+The package ships the `create-issue` skill. Ask pi to write an issue, ask for a change in a repository with `next-issue.config.json`, or run `/skill:create-issue <problem>`. Pi then:
 
 1. restates the problem, reads the code when the problem touches it, and finds the open issues that must be done first;
 2. asks numbered questions until none is open;

package/index.ts

@@ -72,27 +72,28 @@ export function formatStatus(progress: Progress, now: number): string {
   switch (progress.status) {
     case 'running': {
       if (running.length === 0) {
-        return 'next-issue · looking for issues';
+        return 'looking for issues';
       }
+      const count = progress.open === undefined ? '' : `/${progress.open}`;
       const lines = running.map((item) => {
-        const parts = [`#${item.issue}`, item.stage ?? 'prepare', `${item.tools} tools`];
+        const parts = [`#${item.issue}${count}`, item.stage ?? 'prepare', `${item.tools} tools`];
         if (item.startedAt !== undefined) {
           parts.push(duration(now - item.startedAt));
         }
         return parts.join(' · ');
       });
-      return `next-issue ${lines.join(' | ')}`;
+      return lines.join(' | ');
     }
     case 'stopping': {
       const issues = running.map((item) => `#${item.issue}`);
-      return `next-issue ${issues.length === 0 ? '#?' : issues.join(' ')} · stopping`;
+      return `${issues.length === 0 ? '#?' : issues.join(' ')} · stopping`;
     }
     case 'stopped':
-      return `next-issue · stopped: ${outcomes(progress)}`;
+      return `stopped: ${outcomes(progress)}`;
     case 'finished':
-      return `next-issue · finished: ${outcomes(progress)}`;
+      return `finished: ${outcomes(progress)}`;
     case 'failed':
-      return `next-issue · failed: ${progress.error ?? 'unknown error'}`;
+      return `failed: ${progress.error ?? 'unknown error'}`;
   }
 }
 
@@ -354,11 +355,11 @@ export function createExtension(options: Options) {
         const client = shared(options.client);
         await client.attach();
         if (!client.connected) {
-          return report('next-issue · no worker is running', root);
+          return report('no worker is running', root);
         }
         const progress = client.runs[root];
         if (progress === undefined) {
-          return report(`next-issue · no run of ${root}`, root);
+          return report(`no run of ${root}`, root);
         }
         const lines = [
           formatStatus(progress, Date.now()),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ravshansbox/pi-next-issue",
-  "version": "2.17.0",
+  "version": "2.19.0",
   "description": "Pi extension that works through GitHub issues with the next-issue worker",
   "license": "MIT",
   "type": "module",

package/skills/create-issue/SKILL.md

@@ -1,6 +1,6 @@
 ---
 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.
+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, or asks for a change to the code of a repository that has `next-issue.config.json`.
 ---
 
 # Create an issue

package/src/worker.ts

@@ -20,6 +20,7 @@ export type Progress = {
   status: RunStatus;
   issues: IssueProgress[];
   handled: Handled[];
+  open?: number;
   error?: string;
 };