@meowshed/meow-code 0.2.1 → 0.3.0
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 +2 -2
- package/package.json +1 -1
- package/skills/change/SKILL.md +2 -2
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
reader: someone installing or running meow-code on Pi
|
|
3
3
|
answers: what meow-code provides, what it adds to a session and how to install it
|
|
4
4
|
kind: reference
|
|
5
|
-
describes: [@meowshed/meow-code@0.
|
|
5
|
+
describes: [@meowshed/meow-code@0.3.0]
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# @meowshed/meow-code
|
|
@@ -15,7 +15,7 @@ Holds how Claude Code changes code, writes a check and debugs a defect: the smal
|
|
|
15
15
|
pi install npm:@meowshed/meow-code
|
|
16
16
|
```
|
|
17
17
|
|
|
18
|
-
The
|
|
18
|
+
The paw executable ships with `@meowshed/meow-core` alone (REQ-4612): this
|
|
19
19
|
package's launchers run their subcommands through it, so install the core
|
|
20
20
|
package beside this one for the binary-backed checks. Without it, every
|
|
21
21
|
check reports unrun and lets the command through.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@meowshed/meow-code",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"description": "Holds how Claude Code changes code, writes a check and debugs a defect: the smallest correct change, the most precise edit, checks seen failing, and a defect reproduced before any cause is offered. It keeps up to 600 characters in context on every turn. Distributed as a Pi package.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
package/skills/change/SKILL.md
CHANGED
|
@@ -21,7 +21,7 @@ proven by a check that couldn't fail costs every reader after you.
|
|
|
21
21
|
4. After each edit, read the file's diagnostics before you claim anything
|
|
22
22
|
about it.
|
|
23
23
|
5. Prove the change with a check that fails without it, take the evidence
|
|
24
|
-
from the repository's verification
|
|
24
|
+
from the repository's verification stages, and stop when they pass.
|
|
25
25
|
</steps>
|
|
26
26
|
|
|
27
27
|
<rules name="changing code">
|
|
@@ -40,7 +40,7 @@ proven by a check that couldn't fail costs every reader after you.
|
|
|
40
40
|
- E5. Batch reads and edits that don't depend on each other, because each
|
|
41
41
|
round trip costs time and context for nothing.
|
|
42
42
|
- E6. Read a file's diagnostics after editing it and before claiming anything
|
|
43
|
-
about it, and take evidence from the verification
|
|
43
|
+
about it, and take evidence from the verification stages, never from the
|
|
44
44
|
diagnostics, because diagnostics say a file parses, not that the work is
|
|
45
45
|
done.
|
|
46
46
|
- E7. Never reformat while changing behaviour, because in the diff a
|