geniro

Use when scaffolding a reusable workflow-helper (Slack/PR/release automations) or invoking a previously-created action. Stored at .geniro/actions/. Run-mode executes the action directly — invoking it is the authorization, so no confirmation is asked. Skip for editing core Geniro skills — edit the plugin repo directly.

Use when auditing the current repo's AI-assistant instruction files — CLAUDE.md, AGENTS.md, Cursor rules, Copilot instructions, and every other agent-facing surface — for accuracy against the codebase, cross-tool consistency, bloat, structure, and coverage gaps: 'audit our AI instructions', 'is CLAUDE.md stale', 'are the cursor rules consistent with CLAUDE.md', 'clean up AGENTS.md'. Runs a deterministic pre-pass, then parallel dimension reviewers, re-verifies every finding against the cited lines, renders a tiered report, and applies approved fixes only after an action gate. Skip for generating a fresh CLAUDE.md (/geniro:setup), for creating or validating a single .geniro/instructions/ entry (/geniro:instructions), and for mining session history into new rules (/geniro:reflect).

Use when a bug needs systematic investigation. 3-phase loop (Investigate → Propose → Ship) mirroring /geniro:implement: observe → hypothesize → test → isolate → propose fix → author reproduction test, then escalate to /geniro:implement with a handoff file at .geniro/state/handoff/from-debug-{branch}.md. Adversarial mode authors F→P tests against a diff (verify-changes). Skip for bugs with obvious root cause — go straight to /geniro:implement.

Use when shipping a new feature, endpoint, page, or significant change against a spec.md / plan.md (from /geniro:plan) OR a raw inline task description. 3-phase autonomous loop: Analyze → Implement → Self-review-and-Ship.

Use when adding skill-behavior rules at Geniro skill phase boundaries OR cross-cutting code-style rules loaded at every code-writing/review step; also for declaring read-only fact-verification sources (## Data Sources), recording what each project check covers and leaves uncovered so results are not overstated (## Verification Surface), or routing the agent's memory/learnings through a custom backend like an MCP (## Memory Backend). Operations: list, create, edit, validate, delete. Skip for per-file-pattern rules — .claude/rules/.

Use when answering deep codebase questions that need evidence — repo structure, code behavior, git history, or internet sources. Parallel research agents produce cited answers. Skip for bug fixes (/geniro:debug) or codebase mapping (/geniro:onboard).

Use when starting fresh in an unfamiliar codebase and need rapid orientation. Scans structure and conventions; produces _CODEBASE_MAP.md with architecture, module graph, critical paths, entry points. Skip for specific Q&A (/geniro:investigate) or bug investigation (/geniro:debug).

Use when turning a vague idea or feature request into an approved spec.md before /geniro:implement. Spec-first planning workflow: explore → grill (decision-tree clarification) → propose 2-3 approaches → approve sections → write spec.md → mechanical validate → user approve → handoff. Skip for well-formed specs already authored — use /geniro:implement {path} directly. Optional --artifact builds a live, auto-updating visual artifact of the plan as it develops.

Use when restructuring code for better organization or reducing tech debt with zero behavior change. 3-phase loop (Plan → Apply → Verify); never ships — the diff is the deliverable. For behavioral changes use /geniro:implement; for performance use /geniro:review (optimizations dimension).

Use when the user wants to turn recent session experience into project rules, or asks what should be learned from the last sessions. Mines session history for durable rule and improvement candidates — recurring user corrections, rejected suggestions, repeated friction — and routes approved candidates to CLAUDE.md / .claude/rules/ / .geniro/instructions/ / ADR / learnings. Pass a search string to mine the past sessions that mention it, --this-session to mine the running session's own corrections, or nothing to pick the most recent working sessions. Skip for questions about the codebase itself (/geniro:investigate) or reviewing a pending diff (/geniro:review).

Use when an open pull request has unresolved review comments (human or bot) and/or failing CI checks and the user wants them handled. Triages each one, declines the over-engineering and regression-risk asks with an evidence-backed push-back, confirms anything that changes behavior, applies the accepted fixes itself, then posts the replies and resolves the threads. Skip for reviewing a fresh diff (use /geniro:review) or fixing a located bug with no PR feedback (use /geniro:debug or /geniro:implement).

Use when a comprehensive code review of pending changes (a diff, branch, or PR) is needed. Reporter workflow: triage, a cheap mechanical pre-pass, then parallel single-dimension reviewers (bugs, security, architecture, tests, regressions, conventions, and more, plus any custom ones) whose findings are filtered and individually verified, then persisted. Emits a handoff file at .geniro/state/handoff/from-review-{branch}.md; downstream consumers (/geniro:implement, or the user manually) apply the fixes and author any confirming tests — review never edits code itself, and asks before posting to a PR.

Use when starting on a new codebase or after a major plugin update. Detects tech stack, generates a project-specific CLAUDE.md (stack, commands, conventions, domain), and validates it. Re-run mode runs a migration sweep. Singleton bootstrap.

Use when the status line shows a plugin update is available, or to manually pull the latest Geniro plugin version. Verifies plugin integrity, ensures user-authored .geniro/instructions/ and .geniro/actions/ survived intact, and walks any breaking changes in MIGRATION.md.