The rolling release PR sits open accumulating every merge to master, so a
ready-for-review PR misrepresents its state and invites an accidental merge.
draft-pull-request makes readiness an explicit act: mark it ready when you
actually intend to cut the version.
The workflow_dispatch CI kick attached its `checks` run to the release
branch head SHA, but GitHub never counted it in the PR's status rollup, so
branch protection still saw the required check as missing. What actually
unblocks the release PR is approving the queued `action_required`
pull_request run. Removing the step and its `actions: write` grant so the
workflow no longer implies a guarantee it does not provide.
- validate-skill-sync.sh: hard-error when plugin.json version != SKILL.md
metadata.version, or plugin.json description is a YAML block marker
- new scripts/check-skill-version-bumps.sh (bun run version:check): CI fails
when a skill's content changes without a metadata.version bump vs base
- CI: fetch-depth 0 + version:check step after validate
- sync 12 drifted plugin.json versions to SKILL.md; fix turborepo/html-style
junk descriptions
- bundle plugin.json + marketplace.json versions now come from
package.json / skill plugin.json instead of hardcoded 1.0.0
- fixtures + regression tests for both validator gates
Issue Governance failed on every issue opened in the last batch (#97-#101)
with gh's item-edit usage text. The step added the issue to the board, threw
away the item id that item-add returned, and re-ran the paginated items query
to find it again. That query reads a replica that lags behind the write, so
it came back empty, ITEM resolved to the empty string, and
'item-edit --id ""' failed before any field was set — leaving those issues
on the board with no Priority, no Type, and no needs-triage label.
Keep the id from item-add, and hard-fail with a readable message if the id
still cannot be resolved rather than calling item-edit with a blank --id.
Implements three independent enhancements (#39, #26, #27):
#39 codex-image-gen skill (ai-agents bundle)
- New skill that drives the Codex CLI image tool and extracts the finished
PNG from the session rollout JSONL (the headless `codex exec` path never
writes the image to disk). Ships SKILL.md, plugin.json, and a Python
extractor helper, plus an AppIcon.appiconset worked example and the
alias/sandbox, size/alpha, and fragility caveats.
#26 dispatch:plan planning gate
- New plan-dispatch.yml: a human applies `dispatch:plan` to a Backlog issue;
the Claude lane runs the writing-plans contract, posts/updates a trusted
`## Implementation Plan` comment, moves the board to Human Review, assigns
the gate-applier, and applies NO execution gate. Planning and execution stay
separated by human validation.
- setup-dev-loop.sh seeds the dispatch:plan label and installs the workflow.
- Documented in triage-labels.md, setup-agent-routing, loop.md, ai-dev-loop.md
(incl. HITL issues never receiving any gate, dispatch:plan included).
#27 local /codex-loop command
- Codex twin of /loop: claims one dispatch:codex Backlog issue, runs the
executing-plans contract through `codex exec`, opens a PR, hands off to
Human Review. Same 30-min claim lock, reads the `## Implementation Plan`
comment, one issue per invocation. loop.md no longer calls the Codex lane
push-only and cross-references /codex-loop.
Bundles + marketplace.json regenerated; README counts updated (147 skills,
21 commands). All gates green: bun run validate, bun run lint (markdownlint +
biome + shellcheck), actionlint.
GitHub can't block issue creation on missing fields, so enforce continuously:
- .github/workflows/issue-governance.yml — on every issue event, ensure the
issue is on the Dev Loop board (#7) and auto-fill any empty field (Status=Backlog,
Priority=P2, Type=Task), then label needs-triage + comment so a human sets real
values. Idempotent: only writes when a field is empty. Needs PROJECTS_TOKEN
(project-scoped PAT) — default GITHUB_TOKEN can't write an org board.
- .github/ISSUE_TEMPLATE/ — Feature/Bug/Task forms set the native issue Type and
add the issue to the board at creation; blank issues disabled so every issue
starts typed + boarded.
* feat(dev-loop): add ready-for-agent dispatch + setup-agent-routing skill
Human-gated autonomous execution for the AI dev loop, in two phases that share
one dispatch contract: an issue runs only when a human applies `ready-for-agent`
(opt-in) and it sits in `status:todo`.
- setup-agent-routing: new skill that writes an `## Agent skills` routing block
+ docs/agents/ so the dev-loop skills (executing-plans, feature-intake,
writing-prds, qa-reviewer) know a consumer repo's tracker, label vocabulary,
and domain layout. Adapted port of setup-matt-pocock-skills.
- commands/loop.md: Phase 1 local pull loop (/loop, --status, --list) wrapping
executing-plans. One invocation = one task, never a daemon.
- .github/workflows/agent-dispatch.yml: Phase 2 push dispatch on the
`ready-for-agent` label. OAuth-token-only auth (never ANTHROPIC_API_KEY),
per-issue concurrency, least-privilege permissions, untrusted issue body.
- executing-plans: candidate query now requires ready-for-agent + status:todo;
completion strips the gate; QA reject re-arms it (status:todo + ready-for-agent).
- .github/actionlint.yaml: register the Blacksmith runner label (also clears the
pre-existing false positive on generate-bundles.yml).
- Regenerate bundles + marketplace.json (session bundle 6 -> 7 skills).
* feat(dev-loop): add Codex/GPT lane + model-as-variable + setup script
Extend the ready-for-agent loop into a two-engine design:
- New codex-dispatch.yml: ready-for-codex gate routes to openai/codex-action@v1
(sandbox: workspace-write, safety-strategy: drop-sudo). The executing-plans
contract is inlined into the prompt since codex-action has no plugin-loading
equivalent; Codex auto-reads AGENTS.md/.codex. At most one gate per issue.
- Model selection is now a repo VARIABLE, not hardcoded or secret. Claude lane:
claude_args --model vars.AGENT_MODEL (fallback sonnet-4-6). Codex lane:
vars.CODEX_MODEL / vars.CODEX_EFFORT. Only auth tokens stay secret.
- scripts/setup-dev-loop.sh: one-shot per-repo provisioning — seeds labels
(incl. ready-for-codex), installs both workflows, arms CLAUDE_CODE_OAUTH_TOKEN
+ OPENAI_API_KEY, prints the gh variable set commands. --dry-run/--skip flags.
- Docs: AI-DEV-LOOP.md two-lane rewrite + planner/executor/QA role table;
setup-agent-routing SKILL + triage-labels seed gain the ready-for-codex gate;
commands/loop.md notes /loop is the Claude lane (Codex is push-only).
Verified: validate, shellcheck, markdownlint, actionlint all green.
* feat(skills): store implementation plans as issue comments, not local docs/plans files
writing-plans (ported from obra/superpowers) was saving the plan to a local
docs/plans/YYYY-MM-DD-<feature>.md file. That file desyncs from the project the
moment work starts and never crosses to CI, so the cross-engine "Claude plans ->
Codex executes" handoff silently failed on the plan path.
Now the plan is posted as a `## Implementation Plan` comment on the work/PRD
issue, mirroring how writing-prds stores the PRD in the issue body. A comment
co-locates plan + PRD on one issue while keeping the PRD body clean (feature-intake
forbids plans in the body). The executor and both dispatch lanes already read the
issue body, linked PRD, and ALL comments, so the plan reaches CI for either engine
with no executor/workflow/label change — the handoff gap closes for free.
- writing-plans: "Saving the Plan" -> "Storing the Plan" (gh issue comment
--body-file -); killed the docs/plans default; confirm-before-post; no-tracker
fallback; >65k-char split note; label-driven Execution Handoff; version 1.0.0 -> 1.1.0
- writing-plans/README: recorded the storage divergence so future upstream syncs preserve it
- executing-plans: the `## Implementation Plan` comment is the authoritative plan
- AI-DEV-LOOP: both planning artifacts live on the issue (PRD=body, plan=comment)
- writing-prds: "plan the X PRD" flow points at the plan comment
- regenerated planning + session bundles
- Changed project name to "claude-plugin-shipshitdev" and updated versioning in package.json.
- Revised project description to highlight 100+ AI agent skills for indie developers.
- Added repository and bug tracking links in package.json.
- Enhanced README.md with installation instructions for various platforms and added npm version badge for visibility.
- Updated symlink paths in the manual installation section for clarity.
Total sessions today: 4
Vincent