claude

qualityflow

AI-powered QE test planning and code generation — Jira ticket or GitHub issue to STP, STD, and working tests.

4 on GitHubby Guy Oronv0.1.0Apache-2.0updated today

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin qualityflow in redhat-community-ai-tools/qualityflow. Commands read from the repo's manifest — today.

What it installs

Skills (25)

  • comment-classifier

    Classify PR review comments on STP/STD documents into auto-fixable vs needs-human categories. Maps free-text feedback to QualityFlow domain rules for automated fix routing.

  • feature-finder

    Discover code entry points from Jira data when no PR data exists

  • jira-parser

    Parse and normalize Jira issue fields into a structured format for STP generation

  • link-resolver

    Build a dependency graph from Jira issue links and identify key dependencies

  • lsp-tracer

    Trace call graphs using the Claude Code LSP tool to identify regression impact

  • output-validator

    Validate STP document structure and content completeness

  • pii-sanitizer

    Sanitize PII and sensitive data from STP documents

  • pipeline-state

    Track per-ticket QualityFlow pipeline state across all phases. Use when a command needs to initialize state, transition phases, validate prerequisites, detect stale state, or suggest the next step for a ticket.

  • polarion-migration

    Migrate a team's non-automated Polarion test cases into its tests repo as STD design stubs, driven by the team's profile — a case ledger from the CSV export, agent triage, team review, std-builder stubs placed per team, one tests-repo PR per team, and a Polarion reconciliation proposal for the owner

  • pr-analyzer

    Analyze GitHub PR diffs and extract meaningful changes and coverage gaps for STP generation

  • project-resolver

    Resolve issue input (Jira ID or GitHub issue) to project configuration and load project context

  • requirement-mapper

    Map Jira requirements to testable scenarios with validation gates

  • review-rules-extractor

    Extract project-specific review rules dynamically from config files and optional repo scanning

  • scenario-builder

    Build concise test scenario descriptions for STP requirements mapping

  • std-generator

    Generate comprehensive v2.1-ENHANCED STD YAML with pattern metadata, variables, test structure from ALL STP scenarios (single file)

  • std-orchestrator

    Orchestrate STP → STD pipeline (generates comprehensive STD YAML only)

  • std-reviewer

    Semantic QE review of STD YAML and test stubs against STP traceability, pattern correctness, and PSE quality

  • stp-reviewer

    Semantic QE review of STP documents against domain rules, Jira source data, and quality standards

  • stub-generator

    Generate test stubs with PSE docstrings from STD YAML — language and framework driven by project config

  • table-generator

    Generate properly formatted markdown tables for STP documents

  • template-engine

    Apply the official STP template structure to generated content

  • test-generator

    Generate working test code from STD YAML — language and framework driven by project config

  • test-strategy-resolver

    Detect test conventions from a codebase to drive test generation without tier config

  • ticket-assessor

    Assess Jira ticket data completeness and readiness for STP generation

  • tier-classifier

    Classify test scenarios into project-defined tiers

Slash commands (13)

  • /qualityflow:add-repo

    Add a repository to a project's config (tests repo, design-docs repo, or an extra repo QualityFlow reads for context) with every field the pipeline needs

  • /qualityflow:approve

    Approve (or reject) a reviewed STP or STD so the next phase can run — the CLI counterpart of the dashboard's Approve button

  • /qualityflow:demo-pipeline

    Run the full QualityFlow pipeline end-to-end (STP → STD → Go Tests → Python Tests) with demo-friendly phase banners and pauses

  • /qualityflow:fix-pr

    Fix STP/STD documents in a PR based on review comments from humans or bots

  • /qualityflow:generate-tests

    Generate working test implementations from STD YAML

  • /qualityflow:push-pr

    Open or update the pull requests that put a ticket's STP in the team's design-docs repo and its generated tests in the team's tests repo — never in the QualityFlow repo

  • /qualityflow:refine-std

    Iteratively refine an STD (YAML + test stubs) by running review, fixing findings, and re-reviewing until approved

  • /qualityflow:refine-stp

    Iteratively refine an STP document by running review, fixing findings, and re-reviewing until approved

  • /qualityflow:review-std

    Review a generated STD (YAML + test stubs) for traceability, pattern correctness, and code readiness

  • /qualityflow:review-stp

    Review a generated STP document for QE quality, rule compliance, and requirement coverage

  • /qualityflow:std-builder

    Generate STD (YAML + test stubs with PSE docstrings) from an existing STP file or a scenario list, then auto-run review and refinement so the command finishes with a reviewed STD

  • /qualityflow:stp-builder

    Generate a Software Test Plan (STP) from a Jira ticket, then auto-run review and refinement so the command finishes with a final STP. When the team already has an STP for the ticket in its design-docs repo, use that one instead

  • /qualityflow:stp-cursor

    Cursor-native STP generation - the main agent orchestrates the stages itself instead of delegating to the stp-orchestrator subagent

Subagents (18)

  • document-formatter

    Format, validate, and sanitize the final STP document

  • github-issue-collector

    Collect comprehensive GitHub issue data including linked issues, PRs, and cross-references

  • github-pr-fetcher

    Fetch GitHub PR details, diffs, and review comments

  • jira-collector

    Collect comprehensive Jira issue data including linked issues and PR URLs

  • polarion-triager

    Triage one Jira requirement's Polarion test cases for migration — gather the requirement's context, then recommend a verdict per case with evidence. Writes the context and verdict files the polarion-migration skill merges.

  • pr-fix-agent

    Fix STP/STD documents based on PR review comments from humans or bots. Classifies comments as auto-fixable or needs-human, applies fixes using QualityFlow skills, validates results, and pushes updated commits.

  • qualityflow

    Unified QualityFlow pipeline agent. Orchestrates the full 7-stage QE pipeline: STP generation, review, refinement, STD generation, review, refinement, and test code generation.

  • regression-analyzer

    Perform LSP-based regression impact analysis on changed code

  • std-builder

    Generate STD (YAML + test stubs with PSE docstrings) from an existing STP file, or from a scenario list when there is no STP. Produces internal STD YAML and test stubs for all configured languages.

  • std-refiner

    Iteratively refine an STD (YAML + test stubs) by running review, fixing findings, and re-reviewing until approved.

  • std-reviewer

    Review a generated STD (YAML + test stubs) for traceability, pattern correctness, and code generation readiness.

  • stp-builder

    Generate a Software Test Plan (STP) from a Jira ticket using the QualityFlow pipeline. Runs project resolution, Jira collection, GitHub PR fetching, regression analysis, STP generation, and document formatting.

  • stp-generator

    Generate the STP document from collected Jira, GitHub, and regression data

  • stp-orchestrator

    Coordinate the complete STP generation workflow from Jira tickets

  • stp-refiner

    Iteratively refine an STP document by running review, fixing findings, and re-reviewing until approved. Autonomous self-improvement loop.

  • stp-reviewer

    Review a generated STP document for QE quality, rule compliance, and requirement coverage. Fetches Jira data for comparison.

  • test-generator

    Generate working test implementations from STD specifications. Reads project config to determine language and framework. Unified agent supporting all configured languages.

  • ticket-context-analyzer

    Perform targeted LSP analysis on test repositories to extract fresh, contextual patterns for a specific Jira ticket

View source on GitHub

Similar plugins

Collection of example skills demonstrating various capabilities including skill creation, MCP building, visual design, algorithmic art, internal communications, web testing, artifact building, Slack GIFs, and theme styling

19 skills

anthropics/skills 193,780

Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification

1 command · 6 agents

anthropics/claude-code 155,476

storybook

claudecodex

Build, preview, and test UI components with Storybook.

7 skills

storybookjs/storybook 91,552

Agentic QE (external: maintained in proffesor-for-testing/agentic-qe, pinned to v3.15.17): a quality-engineering fleet with 11 QE agents, 9 skills, 9 commands, the agentic-qe MCP server pinned to the plugin version, and the aqe-mod guard that refuses destructive operations on AQE learning data

9 skills · 9 commands · 11 agents · 1 MCP server

ruvnet/ruflo 81,589

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Maintain qualityflow?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted