QA 요청 메시지 생성

Generate structured QA request messages from git diff code changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Vibe-Media-Lab/piklit --skill qa-vibe-media-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: QA 요청 메시지 생성
Source: https://github.com/Vibe-Media-Lab/piklit/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/Vibe-Media-Lab/piklit --skill qa-vibe-media-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of comprehensive QA request messages by analyzing code changes, classifying them, and generating relevant checkpoints, streamlining the pre-QA communication process.

Core Features & Use Cases

  • Automated Change Detection: Identifies modified files using git diff.
  • Intelligent Classification: Categorizes changes into CSS/Style, Components, Services/Utilities, Configuration, or Documentation.
  • Dynamic Checkpoint Generation: Selects relevant QA checks based on the type of code modified (e.g., CSS, components, specific files like openai.js).
  • Standardized Message Formatting: Outputs a ready-to-use QA request message in a clear, copy-paste friendly format.
  • Use Case: After making several CSS and component updates, this Skill generates a QA message that includes specific checks for styling and component integrity, along with general build and lint checks.

Quick Start

Run the qa skill to generate a QA message based on the current git diff.

Frequently Asked Questions about QA 요청 메시지 생성

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

FAQPage Schema
How do I generate a QA request message from git diff?

To generate a QA request message from git diff, this skill analyzes code changes, classifies modified files into categories like CSS or Components, and outputs a formatted message with relevant QA checkpoints for copy-pasting.

How does automated code change detection work for QA testing?

Automated code change detection for QA testing works by running git diff commands to identify modified files, classifying them into categories such as Services or Config, and selecting relevant checkpoints based on those classifications to build a structured request.

Can I automatically categorize file modifications for code review checkpoints?

Yes, you can automatically categorize file modifications for code review. The skill identifies changed files via git diff and sorts them into CSS, Components, Services, Configuration, or Documentation categories to generate specific testing checkpoints.

What is the best way to format QA messages for a QA tab?

The best way to format QA messages is using a standardized output that lists modified files, specifies dynamic checkpoints based on file types, and includes a summary of changes, creating a ready-to-use message for pasting into your QA tab.

Do I need git to classify code modifications and generate testing checkpoints?

Yes, you need git to classify code modifications and generate testing checkpoints. The skill relies on git diff commands to detect the modified files required for categorization and subsequent checkpoint selection.