dev-core

Plugin dev-core in Roxabi/roxabi-plugins. Commands read from the repo's manifest — today.

Skills (32)

• clarify
• R-adr

  Create/list Architecture Decision Records. `--axial` elicits the Axis of Decomposition ADR.

• R-adversarial

  Red-team / devil's advocate on analyses, proposals, architecture, ideas, specs, or plans — attack assumptions, kill vacuous claims, surface bypass and failure modes. Triggers: "adversarial" | "red team" | "devil's advocate" | "attack this design" | "kill this idea" | "stress test this" | "what break

• R-advisory

  Constructive expert advisory on analyses, proposals, architecture, ideas, specs, or plans — strengthen, prioritize, surface blind spots as recommendations (not red-team). Triggers: "advisory" | "second opinion" | "advise on this" | "strengthen this" | "expert advice" | "advisory review" | "what woul

• R-analyze

  Deep technical analysis — explore existing code, risks, shapes. Triggers: "analyze" | "technical analysis" | "how deep is it" | "deep dive" | "investigate this" | "analyze this feature" | "what are the risks" | "explore the codebase" | "look into this" | "explain the architecture" | "what is the arc

• R-ci-setup

  Set up CI/CD — GitHub Actions workflows, TruffleHog, Dependabot, pre-commit hooks, marketplace plugins. Triggers: "ci setup" | "setup ci" | "configure ci" | "setup hooks" | "setup github actions".

• R-ci-watch

  Watch a CI run with live status + emoji dashboard; dump logs on failure; watch auto-merge if CI green + auto-merge enabled + "reviewed" label. Triggers: "watch ci" | "ci watch" | "watch the ci" | "watch run" | "monitor ci".

• R-cleanup-context

  Audit and clean CLAUDE.md, memory, skills, and rules — resolve every finding (fix/promote/relocate/delete), track recurrences, target bloat=0. Triggers: "cleanup context" | "context audit" | "clean memory" | "drain memory" | "prune memory" | "audit memory" | "consolidate rules" | "spa day" | "memory

• R-cleanup

  Clean git branches/worktrees/remotes after merge-status verification; sweep stuck pipeline labels and orphan CI runs. Triggers: "cleanup" | "clean branches" | "cleanup worktrees" | "remove stale branches".

• R-dev-checkup

  Health check — dev-core config, GitHub, labels, workflows, branch protection, CI. Not host /checkup.

• R-dev-implement

  Execute plan — setup worktree, spawn agents, write code + tests. Triggers: "dev-implement" | "implement" | "build this" | "execute plan" | "start coding" | "write the code" | "code this up" | "let's build it" | "build it out" | "/R-dev-implement". Not the host native /implement.

• R-dev-init

  Initialize project — env-setup, ci-setup, release-setup + axial ADR. Not host /init.

• R-dev-plan

  Implementation plan — tasks, agents, file groups, dependencies. Triggers: "dev-plan" | "plan this" | "implementation plan" | "break it down" | "plan this feature" | "how should we build this" | "make a plan" | "create a plan" | "break this down into tasks" | "task breakdown" | "/R-dev-plan". Not the

• R-dev-review

  Multi-domain code review (agents + Conventional Comments → findings + verdict). Triggers: "dev-review" | "code review" | "review changes" | "review PR #42" | "check my code" | "review my changes" | "review this PR" | "do a code review" | "review the diff" | "look at my code" | "/R-dev-review". Not t

• R-dev

  Workflow orchestrator — single entry point for the full dev lifecycle. Triggers: "dev" | "start working on" | "work on issue" | "work on #" | "develop" | "pick up issue" | "tackle issue" | "let's work on".

• R-doc-sync

  Sync project docs after a code change — stale references, affected sections.

• R-env-setup

  Set up local dev environment — stack.yml, AGENTS.md Critical Rules, docs scaffolding, LSP. Triggered by /R-dev-init or standalone /R-env-setup. Triggers: "env setup" | "setup environment" | "scaffold rules".

• R-fix

  Apply review findings — auto-apply high-confidence, 1b1 for rest, then batch-apply. Triggers: "fix findings" | "fix review" | "apply fixes" | "fix these" | "apply review comments" | "apply the review" | "fix the review issues" | "address review feedback" | "fix PR comments".

• R-frame

  Problem framing — capture problem, constraints, scope, tier. Triggers: "frame" | "frame this" | "what's the problem" | "define the problem" | "scope this out" | "define the scope" | "what are we solving" | "problem statement" | "restate what we are solving" | "recap the issue" | "intent first" | "st

• R-interview

  Structured interview → brainstorm | analysis | spec (with promotion). Triggers: "interview" | "brainstorm" | "let's brainstorm" | "think through this" | "help me brainstorm" | "let's think this through" | "explore ideas".

• R-pr

  Create/update PRs with Conventional Commits title, issue linking & guard rails. Triggers: "create PR" | "open PR" | "submit PR" | "update PR" | "/R-pr --draft" | "open a pull request" | "make a PR" | "open pull request" | "submit a pull request" | "create a draft PR" | "raise a PR".

• R-promote

  Promote staging→main — pre-flight, version bump, changelog, PR and tag.

• R-readme-upgrade

  Audit README, CONTRIBUTING, and plugin READMEs against the developer-tool pattern.

• R-recheck

  Drift-check an issue before work begins — fails fast when code has evolved (git-drift, symbol-missing, dep-resolved). Triggers: "recheck" | "is this issue still valid" | "check drift" | "check issue staleness".

• R-release-setup

  Set up commit standards and release automation — Commitizen, commitlint, semantic-release, Release Please, Lefthook/Husky. Triggers: "release setup" | "setup releases" | "commit standards" | "setup release automation".

• R-seed-community

  Bootstrap OSS community health files (CONTRIBUTING, LICENSE, SECURITY, templates).

• R-seed-docs

  Populate scaffolded architecture/standards docs from AGENTS.md and the codebase.

• R-setup-worktree

  Create + link feature branch to issue, then check out worktree. Triggers: "setup worktree" | "create worktree" | "prepare workspace" | "bootstrap branch".

• R-ship

  Meta-orchestrator to land ready code — commit → PR → code-review → fix loop → reviewed label + ci-watch. Triggers: "ship" | "ship this" | "land this" | "land the PR" | "ship PR" | "submit for merge" | "get this merged" | "ship my branch".

• R-spec

  Solution spec — acceptance criteria, breadboard, slices. Triggers: "write spec" | "spec this" | "solution design" | "what will we build" | "design the solution" | "acceptance criteria" | "define acceptance criteria" | "spec it out" | "write the spec".

• R-stack-setup

  Fill `.dev/stack.yml` via guided discovery.

• R-validate

  Run all quality gates (lint, typecheck, test, env, i18n, license; optional falsify on --full) and produce a structured pass/fail report. Triggers: "validate" | "quality check" | "pre-push check" | "are we green".

Subagents (10)

• R-adversarial

  Red-team / devil's advocate for specs, diffs, analyses, proposals, architecture, and ideas. Attacks assumptions, control effectiveness, vacuous guards, fleet impact, and partial-failure paths. On `/R-dev-review`: also apply an OWASP lens (secrets, injection, auth) — R-security-auditor is not spawned

• R-architect

  Use this agent for system design decisions, cross-cutting architecture, and technical planning across the monorepo. Two modes: **normal** (design + ADRs) and **axial** (read-only N×M / target-axis-trap review against the unique `axial: true` ADR). Axial create/supersede is `/R-adr --axial`, not this

• R-backend-dev

  Use this agent for backend implementation tasks in any framework and ORM. Works with NestJS, Express, Fastify, Django, Rails, and any ORM. <example> Context: User needs a new API endpoint user: "Create an endpoint to fetch user preferences" assistant: "I'll use the R-backend-dev agent to implement t

• R-devops

  Use this agent for infrastructure, CI/CD, dependency management, and configuration tasks. Works with any build orchestrator, formatter, package manager, and deployment platform. <example> Context: CI/CD pipeline issue user: "GitHub Actions is failing on the typecheck step" assistant: "I'll use the R

• R-doc-writer

  Use this agent for documentation creation, maintenance, and AGENTS.md updates. Default write format is plain Markdown (.md). Legacy .mdx is readable but not preferred for new files. <example> Context: New feature needs documentation user: "Document the new auth module" assistant: "I'll use the R-doc

• R-fixer

  Use this agent to fix specific review comments across the entire stack (frontend, backend, tests, config). Receives accepted review findings and applies targeted fixes without writing new features or refactoring beyond what is needed. <example> Context: Review comments have been accepted by the huma

• R-frontend-dev

  Use this agent for frontend implementation tasks in any framework and UI library. Works with TanStack Start, Next.js, Remix, SvelteKit, Nuxt, and any UI component system. <example> Context: User needs a new page or component implemented user: "Implement the user profile page" assistant: "I'll use th

• R-product-lead

  Use this agent for product leadership: requirements gathering, issue triage, prioritization, writing analyses and specs, driving the dev pipeline, and verifying deployed features. <example> Context: New feature needs requirements user: "Gather requirements for the notification system" assistant: "I'

• R-security-auditor

  Audit code for security vulnerabilities, review auth flows, and verify compliance with OWASP top 10. <example> Context: Security review needed before release user: "Audit the authentication module for vulnerabilities" assistant: "I'll use the R-security-auditor agent to perform a security audit." </

• R-tester

  Use this agent to generate tests, validate coverage, and verify test quality. Works with Vitest, Jest, Pytest, Playwright, Cypress, and any test framework. <example> Context: New feature needs tests user: "Write tests for the auth service" assistant: "I'll use the R-tester agent to generate test cov

Hooks (5)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT:-$GROK_PLUGIN_ROOT}/hooks/security-check.cjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT:-$GROK_PLUGIN_ROOT}/hooks/bun-test-guard.cjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT:-$GROK_PLUGIN_ROOT}/hooks/principal-branch-pre.cjs"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT:-$GROK_PLUGIN_ROOT}/hooks/format.cjs"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT:-$GROK_PLUGIN_ROOT}/hooks/principal-branch-post.cjs"