hyperflow

Plugin hyperflow in jeremylongshore/tons-of-skills-marketplace. Commands read from the repo's manifest — 6 days ago.

Skills (18)

• audit

  Use when the user wants a code review on recent changes — quality, spec, security, or performance feedback. Triggers a multi-level (L1-L5) review with a standalone Reviewer; on NEEDS_FIX, offers to apply findings via /hyperflow:plan. Trigger with /hyperflow:audit, "review this change", "review my PR

• background

  Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage `.hyperflow/background/registry.json` and the per-agent output buffers at `.hyperflow/background/<id>.md`. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list

• bridge

  Use when the user wants hyperflow's behavioral rules to apply outside the terminal CLI — in Claude Code Desktop, claude.ai web, or IDE extensions that don't load CLI plugins. Writes a managed doctrine block into the project's CLAUDE.md so autonomy + intent-routing + commit cadence + role separation

• cache

  Use when the user wants to view, search, add, edit, prune, archive, or clear hyperflow memory entries. CRUD interface for `.hyperflow/memory/` — never modifies source code, only memory files. Trigger with /hyperflow:cache, "show memory", "search memory for X", "clear memory", "what does hyperflow re

• deploy

  Use when ready to ship — runs pre-push gates (lint, typecheck, build, tests, security sweep), commits, releases, and pushes. Standalone, never auto-invoked. Push always requires explicit confirmation. Trigger with /hyperflow:deploy, "ship it", "ready to push", "release", "cut a release", "deploy".

• design

  Use when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a landing page, or a visual identity — grounded in researched real-world prior art and free of AI slop. Establishes/extends the design system, invokes the matching local taste skill,

• dispatch

  Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the t

• flush

  Use when the user wants to manually flush a deferred-commit queue from a prior or interrupted chain. Reads .hyperflow/commits-queue/manifest.json, fast-forwards the staging branch onto the user's branch, deletes staging, clears the queue. Recovery interface when a chain crashed before its Step 4 aut

• handoff

  Use when managing a two-session handoff — inspecting, picking up, or reviewing a committed handoff package produced by a session=two scope run. The operator interface over the cross-environment handoff lifecycle (plan in one session, build in another, review back in the first). Trigger with /hyperfl

• hyperflow

  Use when applying Hyperflow's orchestration doctrine in Codex, Antigravity, Grok, or another single-agent surface. Auto-invoke for non-trivial engineering work: build, implement, add, refactor, debug, fix, review, audit, plan, scope, design, brainstorm, ship, or deploy. Trigger with /hyperflow:hyper

• issue

  Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance crite

• plan

  Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases

• pr

  Use when reviewing an incoming GitHub pull request — runs the multi-level (L1-L5) audit against the PR's real diff range, posts findings as one batched review (inline, summary, or local-only), offers the standard fix chain on NEEDS_FIX, and optionally merges. The maintainer-side counterpart to /hype

• scaffold

  Use when starting hyperflow in a new project, refreshing the .hyperflow/ cache, or installing auto-detection shims (AGENTS.md, CLAUDE.md). One-shot project setup; does not start the spec → scope → dispatch chain. Trigger with /hyperflow:scaffold, "init hyperflow", "set up hyperflow", "refresh hyperf

• status

  Use when the user wants a one-screen view of current hyperflow project state — version, profile freshness, memory count, and live progress on every in-flight task. Read-only; never modifies state, never dispatches workers. Trigger with /hyperflow:status, "what is hyperflow doing", "show task progres

• sticky

  Use when the user wants to set auto-routing mode: on (every task-shaped message routes), auto (intent-verb messages route — default), or off (no auto-routing). Intent-detection runs by default; use this skill to expand to full sticky or disable entirely. Trigger with /hyperflow:sticky, "make hyperfl

• trace

  Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find th

• workflow

  Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCo

Subagents (23)

• README
• accessibility-reviewer

  Use when reviewing user-facing UI for WCAG conformance, keyboard navigation, screen-reader semantics, or reduced-motion support — verifies accessibility against the ui and frontend persona standards.

• algorithm-reviewer

  Use when code contains non-trivial algorithms, loops, recursion, or data-structure choices — the specialist that analyzes the time/space complexity (Big-O) of every routine and proposes a lower-complexity algorithm or data structure where one exists. Verifies against the performance and scientific p

• analyst

  Use when a decision needs multi-dimensional analysis — weighing intent/fit, scope/risk, and alternatives before a design or approach is chosen. The synthesis investigator behind spec analysis.

• api-reviewer

  Use when reviewing HTTP/RPC/GraphQL endpoints, request/response contracts, input validation, or error semantics — verifies the API surface against the api persona standards.

• architect

  Use when designing a new system or subsystem, or making a structural change to an existing one — the system-design specialist that decomposes the architecture, sets module/service/component boundaries, analyzes failure modes and data flow, designs frontend behavior at scale (debouncing, virtualizati

• backend-reviewer

  Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.

• brain

  Use when a task has been triaged and the chain needs to decide which specialist agents are responsible — the router consulted once after triage to finalize the reviewer/investigator roster, web-research scope, and fan-out approvals.

• compliance-reviewer

  Use when a change touches PII, regulated data, consent, retention, or audit-trail requirements (GDPR/CCPA/HIPAA/PCI) — verifies regulatory posture against the security and docs persona standards. Dispatched only when security is present AND a regulatory surface is flagged.

• data-ml-reviewer

  Use when reviewing data pipelines, numerical/ML code, model training/inference, or analytics correctness — verifies reproducibility and numerical correctness against the scientific and db persona standards.

• database-optimization-reviewer

  Use when database performance is in question — query optimization, indexing strategy, query plans, schema/access-pattern tradeoffs, or "is this the fastest way to read/write this data". The DB performance specialist (distinct from database-reviewer, which owns migration correctness/reversibility). V

• database-reviewer

  Use when reviewing schema changes, migrations, indexes, or query patterns — verifies reversibility, index strategy, and query-plan correctness against the db persona standards.

• debugger

  Use when finding the root cause of a bug, failing test, or regression — runs systematic 5-Whys and parallel hypothesis testing before any patch. The root-cause investigator behind /hyperflow:trace.

• designer

  Use when designing the visual and experiential surface of a product, or reviewing a UI change for taste — the design specialist that establishes and maintains the project's design system, grounds every screen in researched real-world prior art, combines references and adds deliberate creativity, rou

• devops-reviewer

  Use when reviewing CI/CD pipelines, infrastructure-as-code, container/build config, deployment, or observability changes — verifies operational safety against the devops persona standards.

• frontend-reviewer

  Use when reviewing changes to UI components, hooks, client state, or rendering logic (React/Vue/Svelte) — verifies component correctness, state topology, and render purity against the frontend and ui persona standards.

• mobile

  Use when designing or reviewing a mobile app — React Native, Flutter, native iOS (Swift/SwiftUI), native Android (Kotlin/Compose), or responsive mobile web — the mobile specialist that picks the platform/framework, designs the app architecture (navigation, offline-first, lifecycle-aware state), enfo

• motion

  Use when designing or reviewing how elements move — animations, transitions, scroll-driven effects, gestures, and micro-interactions — the motion specialist that picks the right animation library, holds a 60fps compositor-only budget, applies physics-based springs, respects the design system's motio

• performance-reviewer

  Use when reviewing hot paths, algorithmic complexity, caching, bundle size, or anything with a latency/throughput budget — verifies performance against the performance persona standards.

• researcher

  Use when a task needs external evaluation — surveying libraries, comparing approaches, or gathering current best practices and prior art from the web. The deep external-research investigator.

• searcher

  Use when the chain needs the codebase mapped — locating implementations, call sites, conventions, or affected surfaces — before analysis or implementation. The surface-mapping investigator.

• security-reviewer

  Use when reviewing authentication, authorization, secrets handling, input trust boundaries, or any security-sensitive code path — the standalone security gate that halts the pipeline on a violation. Verifies against the security persona standards.

• vulnerability-reviewer

  Use when assessing dependencies, exploit paths, or known-CVE exposure — the deep security-research specialist that maps the diff against current advisories. Verifies against the security and scientific persona standards.

Hooks (2)

• SessionStart

  sh -c 'hook=session-start; for root in "${CODEX_PLUGIN_ROOT:-}" "${CLAUDE_PLUGIN_ROOT:-}" $(ls -dt "$HOME/.codex/plugins/cache/hyperflow-marketplace/hyperflow"/* "$HOME/.claude/plugins/cache/hyperflow

• PreCompact

  sh -c 'hook=pre-compact; for root in "${CODEX_PLUGIN_ROOT:-}" "${CLAUDE_PLUGIN_ROOT:-}" $(ls -dt "$HOME/.codex/plugins/cache/hyperflow-marketplace/hyperflow"/* "$HOME/.claude/plugins/cache/hyperflow-m

Similar plugins