cf

Plugin cf from marketplace cafekit in haposoft/cafekit. Commands read from the repo's manifest — 8 days ago.

Skills (17)

• cf:adv

  Interview until the user and the agent hold the same picture of the outcome, preview it, then deliver honest evidence-backed advice. It writes only its own reports and previews and never implements what it advises.

• cf:agent-browser

  AI-optimized browser automation CLI with context-efficient snapshots. Use for long autonomous sessions, self-verifying workflows, video recording, and cloud browser testing (Browserbase).

• cf:ask

  Answer questions with evidence. Use when the user asks about project behavior, source code, specs, docs, configuration, dependencies, or external technical information; inspect the repo first, use internet/current docs when repo evidence is insufficient, and ask back only when the question cannot be

• cf:brainstorm

  Shape an unsettled piece of work into a decided one before anyone builds it. Use when the outcome is already agreed but two or more approaches would each satisfy it with meaningfully different consequences — setup cost, migration, failure behaviour, who carries the work afterwards; use it too when a

• cf:code-review

  Review a change for correctness, security, and specification compliance without owning execution proof.

• cf:debug

  Use before fixing any bug, failing test, CI/CD failure, production incident, performance issue, UI regression, flaky test, or unexpected behavior. Diagnostic-only root-cause workflow with evidence, hypotheses, blast-radius mapping, and verification plan.

• cf:develop

  Implement an explicitly requested process-first feature or task, run its real verification, and close it with one evidence owner.

• cf:fix

  Use when asked to FIX a bug, error, test failure, CI/CD issue, type error, lint error, log error, UI issue, or code problem. Uses cf:debug for evidence-first diagnosis before any code change.

• cf:git

  Hapo Native Git Operations & Worktree Management. Handles safe commits, conventional split, branch finish choices, secret scanning, and sibling-branch worktrees locally.

• cf:orca

  Use when the user asks in phrases like "pane Orca", "panel Codex", "theo dõi pane", "gửi terminal bên kia", "Orca worktree", "spawn codex vào worktree", "Orca handoff", or "giao cho agent khác trong Orca", while ORCA_PANE_KEY is set and the session is inside Orca (onorca.dev). Reads, waits on, or se

• cf:research

  Research technical decisions with proportional depth, traceable evidence, explicit uncertainty, and project-fit recommendations.

• cf:scout

  Fast scoped codebase discovery using local search first and user-permitted Explore delegation only for broad independent scopes. Use for file discovery, task context, entrypoints, call paths, and blast radius.

• cf:specs

  Plan a feature before anyone implements it. Use the moment a user asks to add, build, implement, or change a capability: a payment flow, an external integration, a schema change, anything touching more than one or two files. Auth, data, or money risk comes here first even when the request is clear,

• cf:sync

  Synchronize process-first task Status and inline Receipts without inventing proof.

• cf:toaa

  The one above all.

• cf:vibe

  Run one command from a GitHub issue or feature request to a reviewed, ready pull request, and to a merge only with --ship. It chains worktree, plan, implementation or fix, review, tests, docs, PR, and PR review fixes through the existing CafeKit skills, taking the user's gates for that one run.

• cf:web-testing

  Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

Slash commands (1)

• /cf:setup-statusline

  Turn on the CafeKit statusline in your Claude Code user settings

Subagents (14)

• advisor

  Use this agent to run the interview-driven `cf:adv` workflow in an isolated context. It scouts, interviews the user one question at a time until the requirements and expected outcome are locked, relays a preview of that outcome for the user to confirm, then delivers honest advice (what to do, what t

• brainstormer

  Pressure-test a material software architecture choice after the Brainstorm controller has scouted the repository and bounded the user contract. Its report states a single-path conclusion in one line and English labels; keep both when relaying it. Tell it which route applies; the routes are feature d

• code-auditor

  Source Code Auditor. Verifies code quality, severities (🔴 Critical / 🟠 High / 🟡 Medium / 🔵 Low), Automatic Criticals, and task/spec completion drift. Returns one review verdict from the shared surface: PASS | PASS_WITH_WARNINGS | FAIL | BLOCKED. It never runs tests. When it states execution proo

• debugger

  Investigates bugs, incidents, CI/log/DB/performance/frontend failures, traces exact root causes with evidence, and hands off a verification-ready fix plan without implementing repairs.

• deployer

  Deployment Specialist. Manages staging/production deployments, health checks, rollback procedures, and CI/CD pipeline orchestration.

• docs-keeper

  Documentation guardian. Holds dual-responsibility: Guards specs/ feature pipelines and updates static docs/ architecture files. Never invents docs without verification. Operates strictly via UPDATES for global docs.

• git-ops

  Executes staging, committing, and pushing branches using conventional commits conventions. Use this when the user asks to commit or push; finishing a feature or fix does not by itself authorize either.

• implementer

  Primary code execution agent. Receives specifications (spec) from cf:specs or task files and transforms them into production-grade source code. Operates on a Single-Track principle within its workspace (linear inside one working tree; multiple instances may run concurrently in separate isolated work

• inspector

  Codebase structure scanner. Use this agent when you need to quickly scout/inspect the codebase architecture, files, and directories. Specializes in finding relevant files for a given work scope before implementation begins.

• project-manager

  Ecosystem Orchestrator. Aggregates evidence for a process-first feature packet (plan.md, flat task files, receipts, worker and review reports) and reports scope drift, task and receipt status, blockers, and the pending GATE-DONE decision. Use when several tasks or agents have finished and the overal

• researcher

  Evidence researcher for bounded technical decisions, source reconciliation, and project-fit recommendations. Its report opens with its depth and labels every claim; keep both, and its path:line anchors, when relaying it.

• spec-maker

  Build a small process-first feature plan and flat executable task packets, then run evidence-backed adversarial review before implementation.

• strategist

  Autonomous counsel from the strongest model (`fable`) in one run — no session model switch, no user interview. Mention `@strategist` from a lower tier (opus/sonnet/haiku) or spawn it from a stuck subagent for hard design, debugging, or trade-off calls. Advisory-only; returns advice, not code.

• test-runner

  QA execution engine. Runs the smallest adequate real proof and returns one canonical test-proof-v1 handoff without writing task state.

Hooks (15)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/session.cjs"

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/state.cjs"

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/plugin-context.cjs"

• SubagentStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/agent.cjs"

• PreCompact

  node "${CLAUDE_PLUGIN_ROOT}/hooks/precompact.cjs"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/secret-output-guardrail.cjs"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/rules.cjs"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/spec-state.cjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/privacy-block.cjs"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/inspect-block.cjs"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/state.cjs"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/spec-state.cjs"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/spec-gate.cjs"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/state.cjs"

• SubagentStop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/state.cjs"

Similar plugins