@juicesharp/rpiv-pi 0.8.3 → 0.9.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.
|
@@ -50,4 +50,9 @@ export const SIBLINGS: readonly SiblingPlugin[] = [
|
|
|
50
50
|
matches: /rpiv-web-tools/i,
|
|
51
51
|
provides: "web_search + web_fetch tools + /web-search-config",
|
|
52
52
|
},
|
|
53
|
+
{
|
|
54
|
+
pkg: "npm:@juicesharp/rpiv-args",
|
|
55
|
+
matches: /rpiv-args(?![-\w])/i,
|
|
56
|
+
provides: "skill-argument resolver — substitutes $N/$ARGUMENTS in skill bodies",
|
|
57
|
+
},
|
|
53
58
|
];
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@juicesharp/rpiv-pi",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.9.0",
|
|
4
4
|
"description": "Skill-based development workflow for Pi Agent — discover, research, design, plan, implement, validate",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
@@ -47,6 +47,7 @@
|
|
|
47
47
|
"@juicesharp/rpiv-todo": "*",
|
|
48
48
|
"@juicesharp/rpiv-advisor": "*",
|
|
49
49
|
"@juicesharp/rpiv-btw": "*",
|
|
50
|
-
"@juicesharp/rpiv-web-tools": "*"
|
|
50
|
+
"@juicesharp/rpiv-web-tools": "*",
|
|
51
|
+
"@juicesharp/rpiv-args": "*"
|
|
51
52
|
}
|
|
52
53
|
}
|
package/skills/commit/SKILL.md
CHANGED
|
@@ -11,7 +11,7 @@ You are tasked with creating git commits for repository changes.
|
|
|
11
11
|
|
|
12
12
|
## Commit hint
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
`$ARGUMENTS` (empty/literal → infer from history and `git diff`)
|
|
15
15
|
|
|
16
16
|
## Context:
|
|
17
17
|
- **In-session**: If there's conversation history, use it to understand what was built/changed
|
|
@@ -12,7 +12,10 @@ You are tasked with implementing an approved technical plan from `thoughts/share
|
|
|
12
12
|
|
|
13
13
|
## Getting Started
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
- Plan path: `$1` (empty/literal → ask user)
|
|
16
|
+
- Phase scope: `${@:2}` (empty → all phases sequentially; else scope to this phase only)
|
|
17
|
+
|
|
18
|
+
With a plan path in hand:
|
|
16
19
|
- Read the plan completely and check for any existing checkmarks (- [x])
|
|
17
20
|
- Read the original ticket and all files mentioned in the plan
|
|
18
21
|
- **Read files fully** - never use limit/offset parameters, you need complete context
|
|
@@ -20,8 +23,6 @@ When given a plan path:
|
|
|
20
23
|
- Create a todo list to track your progress
|
|
21
24
|
- Start implementing if you understand what needs to be done
|
|
22
25
|
|
|
23
|
-
If no plan path provided, ask for one.
|
|
24
|
-
|
|
25
26
|
## Implementation Philosophy
|
|
26
27
|
|
|
27
28
|
Plans are carefully designed, but reality can be messy. Your job is to:
|