qa

Validate GraphReFly changes via adversarial review and final verification gates.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/graphrefly/graphrefly-ts --skill qa-graphrefly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/graphrefly/graphrefly-ts/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/graphrefly/graphrefly-ts --skill qa-graphrefly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken protocol behavior, regressions, and cross-language inconsistencies by running a rigorous adversarial review and enforcing final correctness checks before changes are accepted.

Core Features & Use Cases

  • Adversarial Code Review: Performs adversarial inspection to catch logic errors, edge-case failures, race conditions, leaks, and missing error handling across the touched code.
  • Cross-Language Protocol Alignment: Validates behavior against the GraphReFly spec, including TS/Python/Rust parity expectations and detection of unhandled protocol sequences.
  • Deterministic Fix Application & Final Gates: Applies approved fixes and runs full test/lint/build (plus the Rust mise run gate QA gate when Rust files are changed), ensuring documentation updates are made unless explicitly skipped.
  • Decision Management: Separates “needs decision” architecture-affecting issues from “auto-applicable” fixes, and logs cross-language decisions for later resolution.

Quick Start

Run the qa workflow for GraphReFly and provide any implementation context; for example: Run qa against the current diff for code review and completion checks.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial code review to catch race conditions and logic errors?

Adversarial code review inspects touched code to catch logic errors, edge-case failures, race conditions, leaks, and missing error handling by running parallel subagent review against the current diff before fixes are applied.

How do I validate cross-language protocol alignment between TypeScript, Python, and Rust?

Cross-language protocol alignment validates behavior against the GraphReFly spec, checking TS, Python, and Rust parity expectations while detecting unhandled protocol sequences and logging cross-language decisions for later resolution.

Can I skip documentation updates during QA and regression prevention?

You can skip documentation updates during QA by passing the --skip-docs flag, otherwise the workflow enforces mandatory documentation updates alongside final test, lint, and build verification gates.

What is the best way to triage auto-applicable fixes versus architecture-affecting issues in code review?

Fix triage separates needs-decision architecture-affecting issues from auto-applicable fixes, presenting patches or deferred findings with a strict HALT before correctly applying approved fixes and running repo-specific gate commands.

Does the QA workflow run the Rust gate command when Rust files are changed?

The QA workflow runs the Rust `mise run gate` QA gate whenever Rust files are changed, alongside full test, lint, and build commands, ensuring deterministic final correctness checks before changes are accepted.

When do I need diff-based repo detection for code review and completion checks?

Diff-based repo detection is required when running QA workflows after implementation changes, enabling the system to identify touched files and perform adversarial review, spec alignment, and final verification across the modified codebase.