@raquezha/norpiv 0.1.0 → 0.2.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/package.json +1 -1
- package/sync/SKILL.md +2 -0
package/package.json
CHANGED
package/sync/SKILL.md
CHANGED
|
@@ -16,6 +16,7 @@ Maintains consistency between local `.workflow` state and the remote source of t
|
|
|
16
16
|
- **Idempotency**: If the remote Pi status already reflects the current local state, do not post or update.
|
|
17
17
|
- **Human safety**: NEVER edit human-authored comments. Only update comments/notes containing the Pi sync marker.
|
|
18
18
|
- **Target ownership**: Sync the executable child issue/MR/PR that the work completed, not the umbrella parent, unless the user explicitly asks for parent status. If the active GitHub issue has sub-issues, verify the PR/body/current request points to the right child before posting.
|
|
19
|
+
- **Hyperlinks**: Always format issue references (e.g. `[#140](https://github.com/owner/repo/issues/140)`), source file paths, git branches, and commit hashes as explicit Markdown hyperlinks in sync comments whenever applicable.
|
|
19
20
|
- **Shell safety**: Never pass markdown bodies inline through shell strings. Write bodies to files and use `--body-file` or JSON `--input` API calls so backticks and `$()` cannot execute.
|
|
20
21
|
|
|
21
22
|
## Living status marker
|
|
@@ -60,6 +61,7 @@ Do **not** use latest-comment ownership as the primary decision. Latest-comment-
|
|
|
60
61
|
Format the message for two audiences:
|
|
61
62
|
- **Stakeholders**: summarize outcome, current state, and next step.
|
|
62
63
|
- **Developers**: list vertical slices, commit/PR/MR links, and verification evidence.
|
|
64
|
+
- **Hyperlinking**: convert issue identifiers (`[#140](url)`), commit hashes (`[\`0011b4b\`](url)`), branch names (`[\`feat/140\`](url)`), and key file paths into explicit markdown hyperlinks so they render as interactive links.
|
|
63
65
|
- **Signature and marker**: always append both the signature and `<!-- pi-sync-marker -->`.
|
|
64
66
|
|
|
65
67
|
### 3. Execution
|