skills.rest
tobilafinhangit
tobilafinhangitCOMMUNITY
Explore all skills by this author →
GitHub

qa-handoff

Merge PRs, post testing guides, move cards, and sync qa-mirror branches.

2|Updated Feb 2, 2026
Search Tags:#software development#github#automated testing#continuous integration#qa handoff
One-click install
npx skills add https://github.com/tobilafinhangit/skill-master --skill qa-handoff-tobilafinhangit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-handoff
Source: https://github.com/tobilafinhangit/skill-master/tree/main/.agent/skills/qa-handoff
Command: npx skills add https://github.com/tobilafinhangit/skill-master --skill qa-handoff-tobilafinhangit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, fizzy, git, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of handing off completed work to QA, ensuring smooth integration and testing with minimal manual intervention.

Core Features & Use Cases

  • Automated Merge: Automatically merges PRs into the integration branch.
  • Testing Guide Posting: Posts a testing guide on the Fizzy card.
  • Card Movement: Moves the card to the QA column.
  • Assigning QA Lead: Assigns Elvis Muchiri as the QA lead.
  • qa-mirror Sync: Synchronizes the qa-mirror branch with the integration branch.
  • Use Case: After a PR is approved, use this Skill to automatically hand off the work to QA, ensuring all necessary steps are taken without manual oversight.

Quick Start

Use the qa-handoff skill to hand off the completed work to QA for the PR #123.

Frequently Asked Questions about qa-handoff

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

FAQPage Schema
How do I automate QA handoff after a pull request is approved?▼

Automating QA handoff involves merging pull requests into an integration branch, posting testing guides on project cards, moving cards to QA columns, and syncing qa-mirror branches without manual intervention.

Does the automated QA handoff process require GitHub and Git?▼

Yes, automating the QA handoff process requires GitHub, Git, and Fizzy to execute pull request merges, update project cards, and synchronize qa-mirror branches.

What is the best way to move cards and assign a QA lead for continuous integration?▼

The best way to move cards and assign a QA lead during continuous integration is to automate the workflow, ensuring the card moves to the QA column and the lead is designated upon PR approval.

How do I sync a qa-mirror branch with an integration branch?▼

You sync a qa-mirror branch with an integration branch by triggering an automated handoff process that merges approved pull requests and synchronizes the qa-mirror branch state.

Can I post a testing guide on Fizzy automatically when handing off work?▼

Yes, you can post a testing guide on Fizzy automatically by integrating an automated QA handoff process that updates the Fizzy card with testing instructions upon PR approval.

When should I not use an automated QA handoff script?▼

You should not use an automated QA handoff script if your software development workflow lacks GitHub, Git, or Fizzy dependencies, or requires manual testing oversight.

Related Skills

Explore More Software Engineering Skills→
LynxLabVNLynxLabVN

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merging.

Official
Advanced
zizzfizzixzizzfizzix

auto-qa-scenarios

Generate a human QA report for merged pull requests grouped by product area.

Community
Advanced
ACuberoACubero

ci-cd-pipelines

Automate Python CI/CD pipelines with GitHub Actions for testing, linting, and releases.

Community
Advanced
joshyorkojoshyorko

fizzy

Automate Fizzy CLI workflows for boards, cards, and columns.

Community
Advanced