PDX-0: docs — reusable loop runner template + PDX-501..505 prompt#197
Merged
Conversation
… prompt RCA: Autonomous /loop runs for ticket batches had no persisted, reusable scaffold, so each run was re-authored ad hoc and the workflow/decisions were not captured for future batches. Fix: Added docs/loops/ with loop-template.md (generic template, how-to, decisions, registry), _example-instance.md skeleton, and pdx-501-505.md ready-to-run prompt with step-scoped ComparisonType sets.
Quality Orchestrator🟢 LOW · No test files mapped. ⚡ quality-orchestrator · |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a small internal documentation “loop runner” scaffold under docs/loops/ to standardize how autonomous /loop runs are authored and executed for batches of PDX tickets.
Changes:
- Introduces a reusable loop prompt template with a decisions table and a prompt registry.
- Adds an example “instance” document to copy/fill for new ticket batches.
- Adds a ready-to-run loop prompt for PDX-501..505 (comparisonType + sf/plugin robustness batch).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| docs/loops/loop-template.md | New template/how-to for loop runs, including a registry of prompts. |
| docs/loops/_example-instance.md | New copyable skeleton for creating a new loop prompt instance. |
| docs/loops/pdx-501-505.md | New concrete loop prompt for the first batch (PDX-501..505). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+3
to
+5
| The reusable scaffold for driving a batch of PDX tickets from build → test → validate → merge, | ||
| one ticket per self-paced `/loop` iteration, on top of this repo's documented dev workflow | ||
| (`.claude/commands/git-workflow.md` + `.claude/agents/dev-git-workflow.md`). |
Comment on lines
+42
to
+44
| AUTHORITATIVE WORKFLOW: follow .claude/commands/git-workflow.md and | ||
| .claude/agents/dev-git-workflow.md exactly (worktree-per-branch, yarn install in | ||
| the worktree, commit format, the compile/test/smoke/lint gate, PR template, |
Comment on lines
+30
to
+33
| AUTHORITATIVE WORKFLOW: follow .claude/commands/git-workflow.md and | ||
| .claude/agents/dev-git-workflow.md exactly (worktree-per-branch, yarn install in | ||
| the worktree, commit format, the compile/test/smoke/lint gate, PR template, | ||
| Copilot handling) — WITH these overrides for this loop: |
RCA: Copilot review found the loop docs referenced .claude/agents/dev-git-workflow.md, which is untracked in git and therefore absent in fresh checkouts and worktrees the loop creates, making the instructions impossible to follow. Fix: Replaced the untracked .claude/agents/dev-git-workflow.md reference with the tracked CLAUDE.md across loop-template.md and pdx-501-505.md; only .claude/commands/git-workflow.md + CLAUDE.md are now cited.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/loops/— a reusable scaffold for driving autonomous/loopruns of PDX ticket batches (build → test → validate → merge) on top of the repo's documented dev workflow.loop-template.md: generic template, how-to, decisions table, and a registry of run prompts._example-instance.md: blank skeleton to copy per batch.pdx-501-505.md: first ready-to-run prompt (MCP dogfooding fixes), with the step-scoped ComparisonType sets baked in.Why
Autonomous loop runs were re-authored ad hoc each time, with decisions/authoritative sources not persisted. This captures the workflow once and makes future batches a copy-fill-run.
Notes
PDX-0(no dedicated ticket).docs/loops/.Test plan