A command that runs a staged technical review process involving quality, testing, architecture, and requirements checks before a release decision. IPD-OMO is the process named in the add-on; its specialized role names are not explained further in the input.
Scan every repo on the machine for guardrails, testing, and observability conformance; audit the deltas semantically; produce a fleet report; and propose canary-first remediation.
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
Run the full Obsidian CLI QA harness. Tests run directly against the registered test vault so the Obsidian CLI can operate against it. Results are snapshotted into a timestamped report dir at the end, then the fixture is restored via git.
Command "matchers" from romilly/claude-code-helpers, covering pyhamcrest custom matchers guide, when to create a custom matcher, spotting opportunities, before - verbose and redundant length check and after - expressive, no length check needed.
Implement one or all tasks from a /plan-tasks plan using TDD. Single task runs inline. All-tasks mode orchestrates sequential subagents — one per task.
Quick Flow for bounded fixes - the full APEX route with Brainstorm skipped and Plan compressed to one task; Analyze trio, delegated execution, eLicit, Verify, challenger and full sniper always run.
Read .cursor/playwright-skills/e2e-dashboard/SKILL.md and follow its instructions exactly. Treat that file's body as your operating instructions for this task. Template files to install live in .cursor/playwright-skills/e2e-dashboard/templates/.
★not rated 1 1mo agoA0 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: