@lifeaitools/rdc-skills 0.35.8 → 0.35.9

package/commands/release.md

@@ -1,60 +0,0 @@
----
-
-description: rdc:release (repo, [version]) - [--patch, --minor, --major, --dry-run] — bump, tag, publish and verify a package
----
-
-# rdc:release — Generic Release
-
-> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
-> Checklist-only output. No raw git/npm/CI dumps.
-> One checklist upfront, updated in place, shown again at end with 1-line verdict.
-
-## Checklist
-
-```
-rdc:release: <repo> vX.Y.Z -> vA.B.C
-[ ] Source path resolved
-[ ] Release metadata read
-[ ] Working tree clean or user-approved dirty scope identified
-[ ] Current version detected
-[ ] New version computed
-[ ] Dry-run gate handled
-[ ] Version files updated
-[ ] Tests/self-test passed
-[ ] Commit created
-[ ] Tag created
-[ ] Branch and tag pushed
-[ ] CI/publish status verified
-[ ] Registry/package/deploy target shows vA.B.C, if applicable
-[ ] Local install/update executed, if applicable
-[ ] Installed/runtime version verified
-[ ] Smoke test passed
-✅ rdc:release <repo>: vA.B.C live and verified
-```
-
-## Rules
-
-- Do not release without explicit user authorization.
-- Prefer repo-local release instructions in `.rdc/release.json`, README, package scripts, or CI workflows.
-- Never force push or bypass hooks.
-- Never declare success without verifying the installed or deployed version.
-
-For a `package`-class target that already resolves through `rdc-harness`
-(a real monorepo subtree, not a standalone repo like this one), its
-`packages/deploy/src/runners/registry-release.mjs` runner already proves the
-"Tests/self-test passed" through "Local install/update executed" steps
-safely — real `npm pack`, isolated-prefix install (never the real global
-store), real verify, and `--live` explicitly gates the actual publish. Where
-applicable, `node C:/Dev/rdc-harness/bin/rdc-harness.mjs deploy <slug>
-[--live]` can supply those checklist rows' evidence directly instead of
-hand-rolling the same pack/install/verify cycle. This does not replace
-version bump/tag/push — the harness CLI does neither.
-
-## RDC Skills Package
-
-After publishing this package to npm, a clean-box install should use:
-
-```bash
-npm install -g @lifeaitools/rdc-skills@latest
-rdc-skills-install --profile core
-```

package/commands/review.md

@@ -1,15 +0,0 @@
----
-name: review
-description: rdc:review () - [--unattended] — post-build gate over tsc, tests, docs and code review
----
-
-# review
-
-Use Skill tool with skill: "review", passing `--unattended` through if given.
-
-> This file previously carried a full duplicate of the procedure now owned by
-> `skills/review/SKILL.md`. The two drifted — this copy was missing the
-> mandatory code-review gate (step 8b) and the `engineering-behavior.md` read
-> that the other had. One home for the content closes that class of bug
-> permanently rather than requiring the next editor to remember to update
-> both.

package/commands/status.md

@@ -1,85 +0,0 @@
----
-name: status
-description: rdc:status () — snapshot open epics, health, blockers and next action
----
-
-> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
-> Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
-> One checklist upfront, updated in place, shown again at end with a 1-line verdict.
-
-> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md`).
-
-
-# rdc:status — Project Dashboard
-
-## When to Use
-- Start of any session
-- Project lead asks "what's the status", "where are we", "what's open"
-- Before deciding what to work on next
-
-## Procedure
-
-1. **Open epics:**
-   ```sql
-   SELECT get_open_epics();
-   ```
-
-2. **Work item counts by status:**
-   ```sql
-   SELECT status, count(*) FROM work_items 
-   WHERE status != 'archived' 
-   GROUP BY status ORDER BY status;
-   ```
-
-3. **Items by label/project (top 10 labels):**
-   ```sql
-   SELECT unnest(labels) as label, count(*), 
-          count(*) FILTER (WHERE status = 'done') as done,
-          count(*) FILTER (WHERE status = 'todo') as todo,
-          count(*) FILTER (WHERE status = 'in_progress') as wip
-   FROM work_items 
-   GROUP BY label ORDER BY count DESC LIMIT 10;
-   ```
-
-4. **Recent activity (last 48 hours):**
-   ```sql
-   SELECT title, status, updated_at 
-   FROM work_items 
-   WHERE updated_at > now() - interval '48 hours'
-   ORDER BY updated_at DESC LIMIT 15;
-   ```
-
-5. **Git status:**
-   ```bash
-   git log --oneline -10
-   git status
-   git branch -v
-   ```
-
-6. **Infrastructure health** (if MCP available):
-   - Get infrastructure overview or diagnose issues
-   - Report any apps with failed builds or down containers
-
-7. **Present as a compact dashboard:**
-   ```
-   ## Open Epics (N)
-   <table>
-   
-   ## Work Items: X done | Y todo | Z in_progress
-   
-   ## Recent (48h)
-   <list>
-   
-   ## Deployments
-   <green/red/yellow status>
-   
-   ## Recommended Next
-   <highest priority unstarted epic>
-   ```
-
-## Rules
-- Keep output concise — this is a glance, not a deep dive
-- Always end with a recommendation for what to work on next
-- After the Recommended Next section, suggest which guide file from `.rdc/guides/` (fallback: `.rdc/guides/`) the recommended work would need
-- Use database MCP for queries (not raw curl)
-- If infrastructure MCP is unavailable, skip deployment status and note it