style(skills): finish the dot-slash reference sweep

All intra-skill references are now spelled from the skill root.
checkpoint-preview's step files move into steps/ (matching code-review)
and generate-trail.md into references/ so the whole chain falls under
the file-refs checker; 305 refs verified, both validators clean.
This commit is contained in:
Alex Verkhovsky
2026-08-20 03:25:36 -07:00
parent 2ebb91cd5f
commit 4fa25e8c40
14 changed files with 17 additions and 17 deletions
+1 -1
View File
@@ -62,4 +62,4 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
## FIRST STEP
Read fully and follow `./step-01-orientation.md` to begin.
Read fully and follow `steps/step-01-orientation.md` to begin.
@@ -98,8 +98,8 @@ Omit any metric you cannot compute rather than guessing.
## FALLBACK TRAIL GENERATION
If review mode is not `full-trail`, read fully and follow `./generate-trail.md` to build one from the diff. Then return here and continue to NEXT. If trail generation fails (e.g., git unavailable), the original review mode is preserved — step-02 handles this with its non-trail path.
If review mode is not `full-trail`, read fully and follow `references/generate-trail.md` to build one from the diff. Then return here and continue to NEXT. If trail generation fails (e.g., git unavailable), the original review mode is preserved — step-02 handles this with its non-trail path.
## NEXT
Read fully and follow `./step-02-walkthrough.md`
Read fully and follow `steps/step-02-walkthrough.md`
@@ -80,10 +80,10 @@ When you're ready, say **next** and I'll surface the highest-risk spots.
If at any point the human signals they want to make a decision about this {change_type} (e.g., "let's ship it", "this needs a rethink", "I'm done reviewing", or anything suggesting they're ready to decide), confirm their intent:
- If they want to **approve and ship** → read fully and follow `./step-05-wrapup.md`
- If they want to **reject and rework** → read fully and follow `./step-05-wrapup.md`
- If they want to **approve and ship** → read fully and follow `steps/step-05-wrapup.md`
- If they want to **reject and rework** → read fully and follow `steps/step-05-wrapup.md`
- If you misread them → acknowledge and continue the current step.
## NEXT
Default: read fully and follow `./step-03-detail-pass.md`
Default: read fully and follow `steps/step-03-detail-pass.md`
@@ -83,8 +83,8 @@ You've seen the design and the risk landscape. From here:
If at any point the human signals they want to make a decision about this {change_type} (e.g., "let's ship it", "this needs a rethink", "I'm done reviewing", or anything suggesting they're ready to decide), confirm their intent:
- If they want to **approve and ship** → read fully and follow `./step-05-wrapup.md`
- If they want to **reject and rework** → read fully and follow `./step-05-wrapup.md`
- If they want to **approve and ship** → read fully and follow `steps/step-05-wrapup.md`
- If they want to **reject and rework** → read fully and follow `steps/step-05-wrapup.md`
- If you misread them → acknowledge and continue the current step.
## TARGETED RE-REVIEW
@@ -103,4 +103,4 @@ The human can trigger multiple targeted re-reviews. Each time, present new findi
## NEXT
Read fully and follow `./step-04-testing.md`
Read fully and follow `steps/step-04-testing.md`
@@ -71,4 +71,4 @@ You've seen the change and how to verify it. When you're ready to make a call, j
## NEXT
When the human signals they're ready to make a decision about this {change_type}, read fully and follow `./step-05-wrapup.md`
When the human signals they're ready to make a decision about this {change_type}, read fully and follow `steps/step-05-wrapup.md`
+1 -1
View File
@@ -86,4 +86,4 @@ This uses **step-file architecture** for disciplined execution:
## FIRST STEP
Read fully and follow: `./steps/step-01-gather-context.md`
Read fully and follow: `steps/step-01-gather-context.md`
@@ -91,4 +91,4 @@ Present a summary before proceeding: diff stats (files changed, lines added/remo
## NEXT
Read fully and follow `./step-02-review.md`
Read fully and follow `steps/step-02-review.md`
@@ -29,4 +29,4 @@ failed_layers: '' # set at runtime: comma-separated list of layers that failed o
## NEXT
Read fully and follow `./step-03-triage.md`
Read fully and follow `steps/step-03-triage.md`
@@ -40,4 +40,4 @@
## NEXT
Read fully and follow `./step-04-present.md`
Read fully and follow `steps/step-04-present.md`
@@ -87,4 +87,4 @@ Activation is complete. If `activation_steps_prepend` or `activation_steps_appen
## Execution
Read fully and follow: `./steps/step-01-validate-prerequisites.md` to begin the workflow.
Read fully and follow: `steps/step-01-validate-prerequisites.md` to begin the workflow.
@@ -228,7 +228,7 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN [C continue option] is selected and [all epics and stories saved to document following the template structure exactly], will you then read fully and follow: `./step-04-final-validation.md` to begin final validation phase.
ONLY WHEN [C continue option] is selected and [all epics and stories saved to document following the template structure exactly], will you then read fully and follow: `steps/step-04-final-validation.md` to begin final validation phase.
---
+1 -1
View File
@@ -166,7 +166,7 @@ If the project needs:
Save summary to: `{default_output_file}`
**Done!** Tests generated and verified. Validate against `./checklist.md`.
**Done!** Tests generated and verified. Validate against `checklist.md`.
## On Complete