code-reviewer
コード変更のレビュー専門エージェント。git diffの内容を分析し、バグ・設計問題・品質課題を指摘する。self-reviewスキルから呼び出される。
An agent is a specialist Claude hands a whole job to, with its own tools and its own context.
52 agents across 643 plugins.
コード変更のレビュー専門エージェント。git diffの内容を分析し、バグ・設計問題・品質課題を指摘する。self-reviewスキルから呼び出される。
FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。
All `node tools/apexctl.mjs ...` commands are package-root relative: run them from the packaged skill root, or invoke that script by explicit path.
All `node tools/apexctl.mjs ...` commands are package-root relative: run them from the packaged skill root, or invoke that script by explicit path.
All `node tools/apexctl.mjs ...` commands are package-root relative: run them from the packaged skill root, or invoke that script by explicit path.
Backend Developer - API implementation using patterns, RLS enforcement
Business Systems Analyst - Pattern discovery, spec creation, acceptance criteria definition
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
Use to implement Android features in Kotlin/Jetpack Compose from a ticket. Reads a ticket ID + impl spec, writes the code, writes the tests, opens a…
Use to prepare the store presence — App Store / Play listing copy, keyword research, screenshots, and the store-readiness gate before shipping. Owns…
Use when a ticket needs API or backend work — endpoints, data models, auth, integrations, infra-as-code. Only spawned when backend is in scope per the…
Collects Kubernetes and OCI evidence for the OKE troubleshooter.
Scores troubleshooting hypotheses for OKE incidents using collected evidence.
Resolves OCI load balancer identity and collects LB logging status and issue signals for OKE troubleshooting.
Data Provisioning Engineer - Data pipelines and ETL processes
Use as the top-level orchestrator at the start of any new app project, or when the user wants strategic direction, scope decisions, prioritization tradeoffs,…
Use as the single founder interface — prepares decision briefs, tracks unresolved commitments, ensures every founder decision reaches a specification, and…
Use after a developer finishes a ticket and before tech-manager merges. Reviews a single branch / diff against the impl spec, the engineering principles, and…
Release Train Engineer - PR creation, CI/CD validation, release coordination
Security Engineer - RLS validation, security audits, vulnerability scanning
System Architect - Pattern validation, architectural decisions, conflict prevention
Use after the CEO has set vision, or whenever the project needs product depth — PRD, user stories, acceptance criteria, prioritization, scope cuts, feature…
Use after the CEO sets vision, or whenever the project needs technical strategy — platform choice, architecture, build-vs-buy, technology selection,…
Use to design the analytics event schema, ensure every P0 feature is instrumented, verify the consent gate, and after launch report KPI/funnel/retention…
Technical Delivery Manager - Orchestrates agents, manages blockers, updates Linear
Technical Writer - Documentation creation using documentation patterns
Use to set up and own the repository's plumbing — git branch model, commit/PR conventions, CI, signing, fastlane, build flavors, and secrets handling. Produces…
Use only when incident-ledger.mjs has an open sev1/sev2 record — a production incident, not a routine bug. Owns severity, coordination, containment,…
Use to implement iOS features in Swift/SwiftUI from a ticket. Reads a ticket ID + impl spec, writes the code, writes the tests, opens a PR-equivalent (git…
Use to implement revenue — StoreKit 2 / Play Billing subscriptions and IAP, the paywall gateway, AdMob ads with consent, frequency caps, and NO-AD zones. Owns…
Use before /app-ship on flagship work for the privacy pass — data inventory, consent, retention, third-party sharing, and regional compliance. Distinct…
Use to compose the screens in the ux-architect's inventory — layout, hierarchy, interaction, visual quality — and to own the design tokens and component…
Use for day-to-day product execution below the CPO — clarifying ticket acceptance criteria, grooming docs/11-backlog.md, deciding small in-sprint scope…
Use for independent evidence-gathering on new-product work — user evidence, competitor observation, and the market facts a PRD assumes. Conditional role,…
Use before scope-lock, and again whenever the PRD or the backlog changes materially, to check the derived product documents against the founder's own recorded…
Use to write test plans against the PRD's acceptance criteria, to run end-to-end test passes on a build, and to file bugs. Runs in parallel with development —…
Use before ship on flagship work to attack the product AND the studio's own assumptions — abuse cases, hostile inputs, and the gates that would not have caught…
Use at /app-ship, after release-manager has assembled the release but before anything irreversible happens. Reviews the evidence bundle and the gate record…
Use when the sprint is done and the team wants to prepare a release — assembles a signed, submission-ready build for iOS and Android, owns version bumps, build…
Use on flagship work for the reliability review dimension — offline behaviour, retries, idempotency, sync conflict resolution, state restoration, and recovery…
Use before /app-ship to audit the codebase for shippable-state security issues — credential handling, network safety, data-at-rest, third-party SDKs, OS…
Use to translate architecture into per-platform implementation specs, to design module boundaries, to set patterns the dev pod will reuse, and to make hands-on…
Use to stand up the dev pod, plan sprints, assign work in parallel, run standups, unblock ICs, and track progress. The orchestration layer between executives…
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic