@mr.dj2u/cli 0.1.12 → 0.1.14

package/bundles/codex/skills/workflow-continue-development/SKILL.md

@@ -1,48 +1,48 @@
----
-name: "MDS Continue Development"
-description: "Use when the user asks Mr. DJ's Dev Suite to continue development, pick the next phase task, resume work, or inspect project/todo.md."
----
-
-# Codex Workflow Routing
-
-- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
-- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
-- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
-- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
-
-# /continue-development
-
-Resume work on an onboarded project by following MDS phase order from `project/todo.md`.
-
-## Arguments
-
-- `projectPath`: onboarded app path (default: current directory).
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Call `continue_project` first to get the active-phase brief.
-3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
-4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
-
-## MDS Routing Guardrails
-
-- Treat a request to continue development with MDS as a request for the MDS MCP tool and phase rules first.
-- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
-- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI flow:
-   - `mds continue <projectPath>`
-   - `mds doctor <projectPath>` when blockers are unclear.
-3. If `mds` is not on PATH, invoke the published CLI by binary name:
-   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
-
-## Verification And Output
-
-- Confirm the chosen task belongs to the active phase or has an explicit deferral note.
-- Output: selected next task, blockers, and validation commands to run after implementation.
+---
+name: "MDS Continue Development"
+description: "Use when the user asks Mr. DJ's Dev Suite to continue development, pick the next phase task, resume work, or inspect project/todo.md."
+---
+
+# Codex Workflow Routing
+
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
+- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+
+# /continue-development
+
+Resume work on an onboarded project by following MDS phase order from `project/todo.md`.
+
+## Arguments
+
+- `projectPath`: onboarded app path (default: current directory).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Call `continue_project` first to get the active-phase brief.
+3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
+4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
+
+## MDS Routing Guardrails
+
+- Treat a request to continue development with MDS as a request for the MDS MCP tool and phase rules first.
+- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI flow:
+   - `mds continue <projectPath>`
+   - `mds doctor <projectPath>` when blockers are unclear.
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
+
+## Verification And Output
+
+- Confirm the chosen task belongs to the active phase or has an explicit deferral note.
+- Output: selected next task, blockers, and validation commands to run after implementation.

package/bundles/codex/skills/workflow-create-expo-super-stack/SKILL.md

@@ -1,45 +1,47 @@
----
-name: "MDS Create Expo Super Stack"
-description: "Use when the user asks Mr. DJ's Dev Suite to run the Create Expo Super Stack workflow."
----
-
-# Codex Workflow Routing
-
-- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
-- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
-- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
-- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
-
-# /create-expo-super-stack
-
-Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
-
-## Arguments
-
-- `parentDir`: folder where the new app directory should be created.
-- `appName`: app folder name.
-
-## Required MDS MCP Tool Flow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Drive intake with `create_expo_super_stack_intake_step`.
-3. Ask exactly one question per turn.
-4. Always show the returned default and options.
-5. Never invent or silently accept defaults on the user's behalf.
-6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
-7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
-8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
-
-## Failure Behavior
-
-1. If the guided intake or generate tools are unavailable, stop.
-2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
-3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
-4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
-
-## Verification And Output
-
-- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
-- Confirm `project/todo.md` includes the auto-derived roadmap generated from normalized `project/info.md`.
-- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.
+---
+name: "MDS Create Expo Super Stack"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Create Expo Super Stack workflow."
+---
+
+# Codex Workflow Routing
+
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
+- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+
+# /create-expo-super-stack
+
+Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
+
+## Arguments
+
+- `parentDir`: folder where the new app directory should be created.
+- `appName`: app folder name.
+
+## Required MDS MCP Tool Flow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. If the user pasted or attached `info.md` / project memory, call `create_expo_super_stack_extract_info` first.
+3. Seed the returned answers into `create_expo_super_stack_intake_step` and use intake only for missing or ambiguous questions.
+4. Ask exactly one question per turn.
+5. Always show the returned default and options.
+6. Never invent or silently accept defaults on the user's behalf.
+7. If extraction found the app name, do not ask a second display-name question.
+8. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+9. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+10. Then call `create_expo_super_stack_generate` with `confirmed: true`.
+
+## Failure Behavior
+
+1. If the guided intake or generate tools are unavailable, stop.
+2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
+3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
+4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
+
+## Verification And Output
+
+- Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
+- Confirm `project/todo.md` includes the auto-derived roadmap generated from normalized `project/info.md`.
+- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/bundles/codex/skills/workflow-fix-seo/SKILL.md

@@ -1,42 +1,42 @@
----
-name: "MDS Fix Seo"
-description: "Use when the user asks Mr. DJ's Dev Suite to run the Fix Seo workflow."
----
-
-# Codex Workflow Routing
-
-- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
-- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
-- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
-- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
-
-# /fix-seo
-
-Apply SEO metadata fixes for Expo web routes with MCP guidance and post-fix verification.
-
-## Arguments
-
-- `projectPath`: Expo project path (default: current directory).
-- `routeOrFile`: optional route/file focus for targeted checks.
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Pull `get_skill` for `seo-metadata`.
-3. Optionally run `doctor_scan_file` for focused route files, then `doctor_scan_project` for full checks.
-4. Use `knowledge_list_resources` (`kind: "rule"`) to ensure canonical/indexing strategy is complete.
-5. Implement metadata, canonical, robots, and sitemap corrections in route ownership boundaries.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI checks:
-   - `mds doctor <projectPath> --ci`
-   - Run project-specific web build/preview commands to verify metadata output.
-
-## Verification And Output
-
-- Confirm canonical tags, social metadata, and sitemap/robots behavior on affected routes.
-- Output: changed files, resolved SEO gaps, and any remaining manual verification steps.
+---
+name: "MDS Fix Seo"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Fix Seo workflow."
+---
+
+# Codex Workflow Routing
+
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
+- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+
+# /fix-seo
+
+Apply SEO metadata fixes for Expo web routes with MCP guidance and post-fix verification.
+
+## Arguments
+
+- `projectPath`: Expo project path (default: current directory).
+- `routeOrFile`: optional route/file focus for targeted checks.
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Pull `get_skill` for `seo-metadata`.
+3. Optionally run `doctor_scan_file` for focused route files, then `doctor_scan_project` for full checks.
+4. Use `knowledge_list_resources` (`kind: "rule"`) to ensure canonical/indexing strategy is complete.
+5. Implement metadata, canonical, robots, and sitemap corrections in route ownership boundaries.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI checks:
+   - `mds doctor <projectPath> --ci`
+   - Run project-specific web build/preview commands to verify metadata output.
+
+## Verification And Output
+
+- Confirm canonical tags, social metadata, and sitemap/robots behavior on affected routes.
+- Output: changed files, resolved SEO gaps, and any remaining manual verification steps.

package/bundles/codex/skills/workflow-prepare-deploy/SKILL.md

@@ -1,42 +1,42 @@
----
-name: "MDS Prepare Deploy"
-description: "Use when the user asks Mr. DJ's Dev Suite to run the Prepare Deploy workflow."
----
-
-# Codex Workflow Routing
-
-- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
-- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
-- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
-- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
-
-# /prepare-deploy
-
-Prepare an Expo project for release using deployment-focused skills plus Doctor parity checks.
-
-## Arguments
-
-- `projectPath`: release candidate project path (default: current directory).
-- `includeSeo`: whether to include web metadata/indexing checks (default: `true` when web is targeted).
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Run `doctor_scan_project` in `ci` mode for release parity.
-3. Pull `get_skill` for `deployment`; if web is involved also pull `seo-metadata`.
-4. Use `knowledge_list_resources` (`kind: "rule"`) to confirm env hygiene, SSR safety, and metadata requirements.
-5. Produce a release checklist mapped to current failing checks.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI path:
-   - `mds doctor <projectPath> --ci`
-   - Run project scripts: `lint`, `type-check`, `test`, and production build/profile scripts.
-
-## Verification And Output
-
-- Re-run `doctor_scan_project` (or CLI equivalent) until blockers are cleared.
-- Output: release readiness status, unresolved blockers, and rollback/readiness notes.
+---
+name: "MDS Prepare Deploy"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Prepare Deploy workflow."
+---
+
+# Codex Workflow Routing
+
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
+- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+
+# /prepare-deploy
+
+Prepare an Expo project for release using deployment-focused skills plus Doctor parity checks.
+
+## Arguments
+
+- `projectPath`: release candidate project path (default: current directory).
+- `includeSeo`: whether to include web metadata/indexing checks (default: `true` when web is targeted).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Run `doctor_scan_project` in `ci` mode for release parity.
+3. Pull `get_skill` for `deployment`; if web is involved also pull `seo-metadata`.
+4. Use `knowledge_list_resources` (`kind: "rule"`) to confirm env hygiene, SSR safety, and metadata requirements.
+5. Produce a release checklist mapped to current failing checks.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI path:
+   - `mds doctor <projectPath> --ci`
+   - Run project scripts: `lint`, `type-check`, `test`, and production build/profile scripts.
+
+## Verification And Output
+
+- Re-run `doctor_scan_project` (or CLI equivalent) until blockers are cleared.
+- Output: release readiness status, unresolved blockers, and rollback/readiness notes.

package/bundles/codex/skills/workflow-project-research-plan/SKILL.md

@@ -1,42 +1,42 @@
----
-name: "MDS Project Research Plan"
-description: "Use when the user asks Mr. DJ's Dev Suite to run the Project Research Plan workflow."
----
-
-# Codex Workflow Routing
-
-- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
-- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
-- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
-- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
-
-# /project-research-plan
-
-Turn rough product notes/research into actionable MDS project memory and next-phase plan.
-
-## Arguments
-
-- `projectPath`: target project path (default: current directory).
-- `inputs`: attached notes/docs to normalize into canonical memory files.
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Pull `get_skill` for `research-plan-intake` (and `project-onboarding` when onboarding context is mixed in).
-3. Call `knowledge_list_resources` for `guide` and `reference` resources as needed for structure and validation.
-4. Normalize clear context directly; ask focused follow-up only where ambiguity changes implementation direction.
-5. Update project memory files and produce an implementation-ready next-phase plan.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI fallback:
-   - Use `mds onboard <projectPath>` for structured intake when memory files are missing.
-   - Use `mds continue <projectPath>` after memory normalization to select the next task.
-
-## Verification And Output
-
-- Confirm `project/info.md`, `project/style.md`, and `project/todo.md` align with extracted research context.
-- Output: resolved unknowns, outstanding questions, and the recommended next implementation slice.
+---
+name: "MDS Project Research Plan"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Project Research Plan workflow."
+---
+
+# Codex Workflow Routing
+
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
+- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+
+# /project-research-plan
+
+Turn rough product notes/research into actionable MDS project memory and next-phase plan.
+
+## Arguments
+
+- `projectPath`: target project path (default: current directory).
+- `inputs`: attached notes/docs to normalize into canonical memory files.
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Pull `get_skill` for `research-plan-intake` (and `project-onboarding` when onboarding context is mixed in).
+3. Call `knowledge_list_resources` for `guide` and `reference` resources as needed for structure and validation.
+4. Normalize clear context directly; ask focused follow-up only where ambiguity changes implementation direction.
+5. Update project memory files and produce an implementation-ready next-phase plan.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. Direct CLI fallback:
+   - Use `mds onboard <projectPath>` for structured intake when memory files are missing.
+   - Use `mds continue <projectPath>` after memory normalization to select the next task.
+
+## Verification And Output
+
+- Confirm `project/info.md`, `project/style.md`, and `project/todo.md` align with extracted research context.
+- Output: resolved unknowns, outstanding questions, and the recommended next implementation slice.

package/bundles/codex/skills/workflow-push-merge-loop/SKILL.md

@@ -1,37 +1,37 @@
----
-name: "MDS Push Merge Loop"
-description: "Use when the user asks Mr. DJ's Dev Suite to run the PR iteration loop: doctor, commit, push, poll checks, fix, and merge to test."
----
-
-# Codex Workflow Routing
-
-- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
-- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
-- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
-- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
-
-# /push-merge-loop
-
-Execute the short PR iteration loop for the test branch with strict quality gates.
-
-## Goal
-
-Push intentional changes with a meaningful commit message, open/update a PR to `test`, poll for feedback and failed checks, fix issues, and merge to `test` once all checks are green.
-
-## Loop Rules
-
-1. Run `mds doctor --ci` before any git mutation.
-2. Stage only intentional files and create a meaningful commit message.
-3. Push branch and open or update a PR targeting `test`.
-4. Wait about 2 minutes, then poll PR comments, review threads, and failed checks.
-5. Fix issues locally, rerun Doctor, push updates, and poll again.
-6. Repeat polling/fix cycles up to 5 total iterations.
-7. Merge to `test` only when all required checks are green and no unresolved blocking feedback remains.
-
-## Guardrails
-
-- Do not merge when required checks are failing.
-- Do not skip Doctor between fix cycles.
-- Keep a concise changelog per iteration: what failed, what was changed, what passed.
-- If still failing after 5 cycles, stop and summarize remaining blockers with concrete next actions.
+---
+name: "MDS Push Merge Loop"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the PR iteration loop: doctor, commit, push, poll checks, fix, and merge to test."
+---
+
+# Codex Workflow Routing
+
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
+- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+
+# /push-merge-loop
+
+Execute the short PR iteration loop for the test branch with strict quality gates.
+
+## Goal
+
+Push intentional changes with a meaningful commit message, open/update a PR to `test`, poll for feedback and failed checks, fix issues, and merge to `test` once all checks are green.
+
+## Loop Rules
+
+1. Run `mds doctor --ci` before any git mutation.
+2. Stage only intentional files and create a meaningful commit message.
+3. Push branch and open or update a PR targeting `test`.
+4. Wait about 2 minutes, then poll PR comments, review threads, and failed checks.
+5. Fix issues locally, rerun Doctor, push updates, and poll again.
+6. Repeat polling/fix cycles up to 5 total iterations.
+7. Merge to `test` only when all required checks are green and no unresolved blocking feedback remains.
+
+## Guardrails
+
+- Do not merge when required checks are failing.
+- Do not skip Doctor between fix cycles.
+- Keep a concise changelog per iteration: what failed, what was changed, what passed.
+- If still failing after 5 cycles, stop and summarize remaining blockers with concrete next actions.

package/bundles/codex/skills/workflow-review-expo-project/SKILL.md

@@ -1,42 +1,42 @@
----
-name: "MDS Review Expo Project"
-description: "Use when the user asks Mr. DJ's Dev Suite to run the Review Expo Project workflow."
----
-
-# Codex Workflow Routing
-
-- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
-- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
-- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
-- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
-
-# /review-expo-project
-
-Review an Expo project with MCP-first diagnostics and skill-guided remediation.
-
-## Arguments
-
-- `projectPath`: absolute or relative project path (default: current directory).
-- `mode`: Doctor mode (`fast`, `ci`, or `full`; default: `ci`).
-
-## MCP-First Workflow
-
-1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Call `continue_project` to summarize current project state and blockers.
-3. Call `doctor_scan_project` with `projectPath` and `mode`.
-4. For each warning/error, call `doctor_explain_result`, then pull targeted guidance with `get_skill` (for example: `project-onboarding`, `debugging`, `deployment`).
-5. Call `knowledge_list_resources` with `kind: "guide"` if extra reference context is needed.
-
-## CLI / Manual Fallback
-
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. If MCP still cannot run, use direct CLI flows:
-   - `mds continue <projectPath>`
-   - `mds doctor <projectPath> --ci`
-
-## Verification And Output
-
-- Re-run `doctor_scan_project` (or `mds doctor --ci`) after fixes.
-- Output: blocker summary, failing checks, recommended next task, and concrete follow-up commands.
+---
+name: "MDS Review Expo Project"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Review Expo Project workflow."
+---
+
+# Codex Workflow Routing
+
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
+- Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+
+# /review-expo-project
+
+Review an Expo project with MCP-first diagnostics and skill-guided remediation.
+
+## Arguments
+
+- `projectPath`: absolute or relative project path (default: current directory).
+- `mode`: Doctor mode (`fast`, `ci`, or `full`; default: `ci`).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Call `continue_project` to summarize current project state and blockers.
+3. Call `doctor_scan_project` with `projectPath` and `mode`.
+4. For each warning/error, call `doctor_explain_result`, then pull targeted guidance with `get_skill` (for example: `project-onboarding`, `debugging`, `deployment`).
+5. Call `knowledge_list_resources` with `kind: "guide"` if extra reference context is needed.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client <client> --scope project`
+2. If MCP still cannot run, use direct CLI flows:
+   - `mds continue <projectPath>`
+   - `mds doctor <projectPath> --ci`
+
+## Verification And Output
+
+- Re-run `doctor_scan_project` (or `mds doctor --ci`) after fixes.
+- Output: blocker summary, failing checks, recommended next task, and concrete follow-up commands.