docs(skills): make skill references repo-relative#68
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fd19a48b1a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - Structure references (match level of detail and style): | ||
| - `/Users/davidahmann/Projects/gait/product/PLAN_v1.md` | ||
| - Output file: `/Users/davidahmann/Projects/wrkr/product/PLAN_NEXT.md` (unless user specifies a different target) | ||
| - `gait/product/PLAN_v1.md` (reference only, if available in your environment) |
There was a problem hiding this comment.
Fix relative path to sibling gait style reference
The converted reference path gait/product/PLAN_v1.md resolves under the current repo (wrkr/gait/...), but the original absolute path pointed to a sibling checkout (.../Projects/gait/...), which should become ../gait/product/PLAN_v1.md. In environments where wrkr and gait are side-by-side (the layout implied by the previous path), this change prevents the workflow from finding the style reference and silently drops intended plan-structure guidance.
Useful? React with 👍 / 👎.
Problem
Several skill docs used machine-specific absolute paths (for example
/Users/davidahmann/...), which breaks portability in other workspaces and CI environments.Changes
Validation
make prepush-full./.tmp/wrkr scan -path . --json > .tmp/command-anchor-scan.json