You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gap found during Phase 9 self-audit (create-dev-loop-dev-loop cycle, PR #86)
create-dev-loop-dev-loop's own header states:
Skill repo: dmccoystephenson/create-dev-loop-dev-loop (issues for self-audit findings go here)
Phase 9 step 1 runs gh issue list --repo dmccoystephenson/create-dev-loop-dev-loop --state open, and all gap-issue filing in that phase targets that repo. But it does not exist / is not resolvable via the API:
$ gh repo view dmccoystephenson/create-dev-loop-dev-loop
GraphQL: Could not resolve to a Repository with the name 'dmccoystephenson/create-dev-loop-dev-loop'. (repository)
This blocks Phase 9 entirely — a self-audit cycle has nowhere to file the gaps it finds. Filing this one here instead, on the target repo, as the best available substitute audit trail.
Suggested action
One of:
Create the dmccoystephenson/create-dev-loop-dev-loop repo (with the standard gap-issue labels from Step 6) so Phase 9 has a real target, or
If the intent is for create-dev-loop-dev-loop's self-audit findings to go to the main create-dev-loop repo instead (since this skill is really about dogfooding create-dev-loop on itself), update the skill's header and Phase 9 references accordingly.
This is a meta-issue specific to the generated create-dev-loop-dev-loop skill, not something to fix in create-dev-loop.md itself.
Provenance
Found during the 2026-07-30 cycle that produced PR #86.
Cross-reference: the working tracker repo is dmccoystephenson/cdl-dev-loop (it exists; create-dev-loop-dev-loop still 404s). This cycle's Phase 9 gap was filed there as cdl-dev-loop#25, and the skill-side fix is tracked as cdl-dev-loop#14. Leaving this open — the fix is an edit to the generated skill file, which the loop is not authorized to make autonomously.
Closing as a duplicate, filed on the wrong tracker.
This issue was opened here as "the best available substitute audit trail" on the premise that no tracker repository was reachable. That premise has since been shown to be incomplete: the skill's configured repository name (dmccoystephenson/create-dev-loop-dev-loop) does indeed 404, but a real tracker exists under a different name — dmccoystephenson/cdl-dev-loop — and it already carries the same finding as cdl-dev-loop#14, "Skill points Phase 9 at a nonexistent repo (create-dev-loop-dev-loop); the real one is cdl-dev-loop", filed 2026-07-25 and still open.
Nothing described here is being dismissed — the misconfiguration is real and remains tracked at its canonical location, where the fix (correcting the skill's Skill repo: header and its Phase 9 --repo references) actually belongs. Keeping a second copy on the target repository would only split the discussion across two trackers.
Subsequent self-audit findings are being filed on cdl-dev-loop accordingly.
Activity
dmccoystephenson commentedon Aug 1, 2026
Cross-reference: the working tracker repo is
dmccoystephenson/cdl-dev-loop(it exists;create-dev-loop-dev-loopstill 404s). This cycle's Phase 9 gap was filed there as cdl-dev-loop#25, and the skill-side fix is tracked as cdl-dev-loop#14. Leaving this open — the fix is an edit to the generated skill file, which the loop is not authorized to make autonomously.dmccoystephenson commentedon Aug 8, 2026
Closing as a duplicate, filed on the wrong tracker.
This issue was opened here as "the best available substitute audit trail" on the premise that no tracker repository was reachable. That premise has since been shown to be incomplete: the skill's configured repository name (
dmccoystephenson/create-dev-loop-dev-loop) does indeed 404, but a real tracker exists under a different name —dmccoystephenson/cdl-dev-loop— and it already carries the same finding as cdl-dev-loop#14, "Skill points Phase 9 at a nonexistent repo (create-dev-loop-dev-loop); the real one is cdl-dev-loop", filed 2026-07-25 and still open.Nothing described here is being dismissed — the misconfiguration is real and remains tracked at its canonical location, where the fix (correcting the skill's
Skill repo:header and its Phase 9--reporeferences) actually belongs. Keeping a second copy on the target repository would only split the discussion across two trackers.Subsequent self-audit findings are being filed on
cdl-dev-loopaccordingly.This comment was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).