@herbcaudill/ralph 0.6.4 → 0.6.5
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 +1 -1
- package/templates/prompt-beads.md +23 -21
package/package.json
CHANGED
|
@@ -1,42 +1,44 @@
|
|
|
1
|
-
|
|
1
|
+
### Step 1: Check for errors
|
|
2
2
|
|
|
3
|
-
If there are build errors or test failures:
|
|
3
|
+
Run `pnpm test:all`. If there are build errors or test failures:
|
|
4
4
|
|
|
5
|
-
-
|
|
6
|
-
-
|
|
5
|
+
- Create a P1 issue documenting them.
|
|
6
|
+
- This is your only task.
|
|
7
|
+
- Proceed to Step 4
|
|
8
|
+
|
|
9
|
+
### Step 2: Check for open issues
|
|
10
|
+
|
|
11
|
+
Run `bd ready` to list unblocked issues.
|
|
12
|
+
|
|
13
|
+
If there are issues ready to be worked on, proceed to Step 3.
|
|
7
14
|
|
|
8
|
-
If there are
|
|
15
|
+
If there are none:
|
|
9
16
|
|
|
10
|
-
-
|
|
17
|
+
- Immediately output <promise>COMPLETE</promise>.
|
|
18
|
+
- End your turn.
|
|
11
19
|
|
|
12
|
-
|
|
20
|
+
### Step 3: Select a task
|
|
13
21
|
|
|
14
|
-
-
|
|
15
|
-
- End your turn
|
|
22
|
+
Select the highest-priority issue to work on. Use your best judgement.
|
|
16
23
|
|
|
17
|
-
|
|
24
|
+
### Step 4: Work on a single task
|
|
18
25
|
|
|
19
|
-
- Find the highest-priority issue to work on. Use your best judgement.
|
|
20
26
|
- Output `✨ <task name>`.
|
|
21
27
|
- Mark the issue as in progress with `bd update <id> --status=in_progress`
|
|
22
|
-
- Work only on that task. Only work on a single issue in a single turn.
|
|
28
|
+
- Work only on that task. Only work on a single issue in a single turn.
|
|
29
|
+
- If the issue you choose is complex enough that it will take you more than a minute or two, your task is to break it into sub-issues and then end your turn.
|
|
23
30
|
- While you're working, if you notice something else that needs to be done - follow-up tasks, other things that don't seem to be working right - open new issues.
|
|
24
31
|
- Where applicable, add tests to validate your changes and confirm that they pass.
|
|
25
32
|
- Update CLAUDE.md with any relevant changes.
|
|
26
33
|
|
|
34
|
+
### Step 5: Wrap up
|
|
35
|
+
|
|
27
36
|
When you complete a task:
|
|
28
37
|
|
|
29
38
|
- Run `ppnpm format`.
|
|
30
|
-
- Run `pnpm
|
|
39
|
+
- Run `pnpm test:all && pnpm build`.
|
|
31
40
|
- Commit and push your work.
|
|
32
|
-
- Record a summary of the changes you made as a comment in the issue with `bd comments <id>
|
|
41
|
+
- Record a summary of the changes you made as a comment in the issue with `bd comments add <id> "...markdown summary of changes"`.
|
|
33
42
|
- Close the issue: `bd close <id>`.
|
|
34
43
|
- Output `✅ <task name>`.
|
|
35
44
|
- End your turn.
|
|
36
|
-
|
|
37
|
-
### Commit message format
|
|
38
|
-
|
|
39
|
-
```
|
|
40
|
-
<concise summary of changes> (<issue id>)
|
|
41
|
-
<more detailed summary of changes>
|
|
42
|
-
```
|