QA Handoff

Update a ticket with what shipped and tell QA what to test, in lean, empathetic, user-journey language. Verifies what is actually merged, released and deployed, maps each change to the ticket it fixes, writes a short status (in production / open / left, by owner) and a numbered list of user journeys to test with expected outcomes and what to report. Use when a change is merged or deployed and someone asks "what should QA test", "update the ticket", "post what we merged", "is this live", or wants a tester note, release note or status comment for any tracker (Linear, Jira, GitHub Issues).

5 stars 2 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill qa-handoff
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/qa-handoff ~/.claude/skills/qa-handoff

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# QA handoff: lean ticket update + what to test

The reader is a tester or a product person who knows the product, not the code. On the first
pass they want four things: **what changed for users, the rule behind it, what to try, and what
to report.** Everything else is noise.

**The PR and the handoff describe the same change from two sides.** The PR follows the *flow*:
the requests, services, events and code paths a reviewer must reason about. The handoff follows
the *user journey*: who the customer is, what they do, what they see, and the business rule that
decides it. Translate; never paste the PR's flow, diagram or class names into the handoff.

## 1. Establish the facts before writing

Never write "live" or "in production" from memory, or because something merged.

1. **What merged.** Check each pull request's state, merge commit and base branch. A change merged
   into another feature branch (a stacked PR) is not on the main branch yet.
2. **What released.** Find the release tag or build that contains the merge commit
   (`git tag --contains <commit>`, or the pipeline's build for it).
3. **What is deployed.** Check the running version: the deployment tool, the cluster, the
   pipeline, or a telemetry field the change added. If none is reachable, say so in one line
   and name whose word you rely on ("per <person>; release X contains it"). Never hide an
   unverified claim.
4. **Which ticket.** The pull request body, branch name or commits name the ticket. Post on the
Read the full skill on GitHub

Details

Skill name
qa-handoff
Path
plugins/engineering-practices/skills/qa-handoff/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the QA Handoff skill do?

Update a ticket with what shipped and tell QA what to test, in lean, empathetic, user-journey language. Verifies what is actually merged, released and deployed, maps each change to the ticket it fixes, writes a short status (in production / open / left, by owner) and a numbered list of user journeys to test with expected outcomes and what to report. Use when a change is merged or deployed and someone asks "what should QA test", "update the ticket", "post what we merged", "is this live", or wants a tester note, release note or status comment for any tracker (Linear, Jira, GitHub Issues).

How do I install the QA Handoff skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is QA Handoff popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

QA Observability

8

Freddy-CHEN-ux/00_claude_skills

Observability for quality engineering: using logs, metrics, and traces as test signals; SLI/SLO quality gates; trace-based debugging of failures; and cost-aware instrumentation with OpenTelemetry.

Testing & QA

QA API Testing Contracts

8

Freddy-CHEN-ux/00_claude_skills

API testing and contract validation. Design and execute schema validation, contract tests, negative testing, and change safety for REST, GraphQL, and gRPC APIs. Use when you need API test plans, contract testing, or CI quality gates.

Testing & QA

QA Refactoring

8

Freddy-CHEN-ux/00_claude_skills

Safe refactoring for quality engineering: characterization tests, seam creation, incremental steps, contracts, and CI quality gates to preserve behavior while changing structure.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.