nightralph 0.0.1 → 0.0.2
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 +11 -33
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -23,9 +23,7 @@ so they can't drift as long as you install the skills with this package.
|
|
|
23
23
|
* [Install Dependency Skills](#install-dependency-skills)
|
|
24
24
|
- [Workflow](#workflow)
|
|
25
25
|
* [Create Issues](#create-issues)
|
|
26
|
-
* [Execute
|
|
27
|
-
- [Workflow](#workflow-1)
|
|
28
|
-
* [`nightralph` command](#nightralph-command)
|
|
26
|
+
* [Execute Tasks with `nightralph`](#execute-tasks-with-nightralph)
|
|
29
27
|
|
|
30
28
|
<!-- tocstop -->
|
|
31
29
|
|
|
@@ -75,6 +73,8 @@ Use the `to-tickets` skill to create issues in local markdown files.
|
|
|
75
73
|
grill -> to-spec -> to-tickets -> tdd
|
|
76
74
|
```
|
|
77
75
|
|
|
76
|
+
The `nightralph` CLI does the `tdd` part.
|
|
77
|
+
|
|
78
78
|
>
|
|
79
79
|
> [!NOTE]
|
|
80
80
|
> The `grill -> to-spec` pipeline is recommended to be run in a
|
|
@@ -85,12 +85,17 @@ grill -> to-spec -> to-tickets -> tdd
|
|
|
85
85
|
> [!TIP]
|
|
86
86
|
> The `to-tickets` skill bundled here can use any input text
|
|
87
87
|
> describing a feature, meaning `grill` & `to-spec` skills are not required.
|
|
88
|
+
> You could, for example, use
|
|
89
|
+
> [superpowers:writing-plans](https://github.com/obra/superpowers/blob/main/skills/writing-plans/SKILL.md),
|
|
90
|
+
> then follow with `to-tickets`.
|
|
88
91
|
>
|
|
89
92
|
|
|
90
|
-
### Execute Issues
|
|
91
93
|
|
|
92
|
-
|
|
93
|
-
|
|
94
|
+
### Execute Tasks with `nightralph`
|
|
95
|
+
|
|
96
|
+
After you have the tickets, you can use the `nightralph` loop to execute.
|
|
97
|
+
The `to-tickets` skill produces markdown files at
|
|
98
|
+
`.scratch/<feature>/issues/<NN>-<slug>.md`, with task dependency info.
|
|
94
99
|
|
|
95
100
|
```bash
|
|
96
101
|
# Auto-discover .scratch features and run with claude
|
|
@@ -130,30 +135,3 @@ Notes:
|
|
|
130
135
|
in-place. Failed tickets keep their status and block dependents.
|
|
131
136
|
* Agent logs are written to `<dir>/../logs/<ticket>.log`.
|
|
132
137
|
|
|
133
|
-
|
|
134
|
-
## Workflow
|
|
135
|
-
|
|
136
|
-
Need to use several skills, in order:
|
|
137
|
-
|
|
138
|
-
```
|
|
139
|
-
grill -> to-spec -> to-tickets
|
|
140
|
-
```
|
|
141
|
-
|
|
142
|
-
At that point you will have a number of tickets, which are markdown files
|
|
143
|
-
in your local repo. This tool handles the last step, implementing the tickets,
|
|
144
|
-
which normally is done with the `tdd` skill. This tool will work in a loop,
|
|
145
|
-
aiming to complete 1 task per session, then restarting (a classic Ralph loop).
|
|
146
|
-
|
|
147
|
-
### `nightralph` command
|
|
148
|
-
|
|
149
|
-
After you have the tickets, you can use the `nightralph` loop to execute.
|
|
150
|
-
|
|
151
|
-
```sh
|
|
152
|
-
npx nightralph claude -m claude-opus-4-6
|
|
153
|
-
```
|
|
154
|
-
|
|
155
|
-
Or with a different provider:
|
|
156
|
-
|
|
157
|
-
```sh
|
|
158
|
-
npx nightralph codex -m gpt-5.6-terra
|
|
159
|
-
```
|