qa — for Claude Code community, for Claude Code, ide skills, qa --start, dev-mode, qa --stop, qa --restart, plugin, locally, before

v1.0.0
GitHub

About this Skill

Perfect for Ruby on Rails Agents needing seamless local testing and marketplace switching capabilities. QA the FLOW plugin locally. Switch marketplace to local source, test in a live session, restore when done.

Features

Test the FLOW plugin locally before releasing. Maintainer-only — requires the plugin to be
/qa — show dev mode status, then prompt for next action
/qa --start — nuke cache, switch marketplace to local source, create .dev-mode marker
/qa --stop — nuke cache, restore production marketplace, remove .dev-mode marker
/qa --restart — nuke cache, re-register local source, refresh cache (must alrea

# Core Topics

for Claude Code qa --start dev-mode qa --stop qa --restart plugin
benkruger benkruger
[2]
[0]
Updated: 3/6/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 10/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
10/11
Quality Score
51
Canonical Locale
en
Detected Body Locale
en

Perfect for Ruby on Rails Agents needing seamless local testing and marketplace switching capabilities. QA the FLOW plugin locally. Switch marketplace to local source, test in a live session, restore when done.

Core Value

Empowers agents to test the FLOW plugin locally before releasing, utilizing Ruby on Rails, and providing a seamless way to switch between production and local marketplaces using commands like `/qa --start` and `/qa --stop`.

Ideal Agent Persona

Perfect for Ruby on Rails Agents needing seamless local testing and marketplace switching capabilities.

↓ Capabilities Granted for qa

Testing FLOW plugin locally before release
Switching between production and local marketplaces
Debugging local marketplace issues

! Prerequisites & Limits

  • Requires Ruby on Rails
  • Maintainer-only access
  • FLOW plugin installation required

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is qa?

Perfect for Ruby on Rails Agents needing seamless local testing and marketplace switching capabilities. QA the FLOW plugin locally. Switch marketplace to local source, test in a live session, restore when done.

How do I install qa?

Run the command: npx killer-skills add benkruger/flow/qa. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for qa?

Key use cases include: Testing FLOW plugin locally before release, Switching between production and local marketplaces, Debugging local marketplace issues.

Which IDEs are compatible with qa?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for qa?

Requires Ruby on Rails. Maintainer-only access. FLOW plugin installation required.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add benkruger/flow/qa. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use qa immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

qa

Install qa, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

FLOW QA

Test the FLOW plugin locally before releasing. Maintainer-only — requires the plugin to be installed.

Usage

text
1/qa
2/qa --start
3/qa --stop
4/qa --restart
  • /qa — show dev mode status, then prompt for next action
  • /qa --start — nuke cache, switch marketplace to local source, create .dev-mode marker
  • /qa --stop — nuke cache, restore production marketplace, remove .dev-mode marker
  • /qa --restart — nuke cache, re-register local source, refresh cache (must already be in dev mode)

Flag: --start

Step 1 — Check dev mode

Use the Read tool to check if .flow-states/.dev-mode exists.

If it exists, print "Already in dev mode. Use /qa --stop to exit." and stop.

Step 2 — Nuke cache and switch to local source

Get the project root from git worktree list --porcelain (first worktree line).

Run:

bash
1rm -rf ~/.claude/plugins/cache/flow-marketplace

Then:

bash
1claude plugin marketplace add <project_root>

Then:

bash
1claude plugin marketplace update flow-marketplace

Step 3 — Create dev mode marker

Use the Write tool to create .flow-states/.dev-mode with the content active.

Step 4 — Announce

Print inside a fenced code block:

markdown
1```text
2============================================
3  FLOW QA — DEV MODE ACTIVE
4============================================
5```

Then print:

Plugin cache now contains local source.

Open a new Claude Code session in a target project to test. Run /qa --stop when done.

Flag: --restart

Step 1 — Check dev mode

Use the Read tool to check if .flow-states/.dev-mode exists.

If it does not exist, run the --start flow instead (skip to the --start section above).

Step 2 — Nuke cache and re-register local source

Get the project root from git worktree list --porcelain (first worktree line).

Run:

bash
1rm -rf ~/.claude/plugins/cache/flow-marketplace

Then:

bash
1claude plugin marketplace add <project_root>

Then:

bash
1claude plugin marketplace update flow-marketplace

Step 3 — Announce

Print inside a fenced code block:

markdown
1```text
2============================================
3  FLOW QA — Cache refreshed
4============================================
5```

Then print:

Plugin cache updated from local source.

Open a new Claude Code session in a target project to test.

Flag: --stop

Step 1 — Check dev mode

Use the Read tool to check if .flow-states/.dev-mode exists.

If it does not exist, print "Not in dev mode. Nothing to stop." and stop.

Step 2 — Nuke cache and restore production marketplace

Run:

bash
1rm -rf ~/.claude/plugins/cache/flow-marketplace

Then:

bash
1claude plugin marketplace add benkruger/flow

Then:

bash
1claude plugin marketplace update flow-marketplace

Step 3 — Remove dev mode marker

Use Bash to remove the marker:

bash
1rm .flow-states/.dev-mode

Step 4 — Report

Print inside a fenced code block:

markdown
1```text
2============================================
3  FLOW QA — Dev mode stopped
4============================================
5```

No flag (bare /qa)

Check if .flow-states/.dev-mode exists using the Read tool.

If dev mode is active, print inside a fenced code block:

markdown
1```text
2============================================
3  FLOW QA — Dev mode: ACTIVE
4  Plugin cache is using local source.
5============================================
6```

Then use AskUserQuestion:

"What would you like to do?"

  • Restart QA — refresh cache from local source
  • Stop QA — restore production marketplace

Then invoke the chosen flag (--restart or --stop).

If dev mode is not active, print inside a fenced code block:

markdown
1```text
2============================================
3  FLOW QA — Dev mode: INACTIVE
4  Plugin cache is using production source.
5============================================
6```

Then use AskUserQuestion:

"Start QA dev mode?"

  • Yes, start — runs /qa --start
  • No, cancel — stop

Then invoke --start if chosen.

Related Skills

Looking for an alternative to qa or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

openclaw-release-maintainer is an AI agent skill for openclaw release maintainer.

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is an AI agent skill for use this skill when adding or changing framework feature flags in next.js internals.

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

pr-review is an AI agent skill for pytorch pr review skill.

★ 98.6k
⑂ 0
Developer