qa은(는) 무엇을 하나요?
대화형 QA 세션에서 사용자가 버그나 이슈를 대화식으로 보고하면, 에이전트가 GitHub 이슈를 등록합니다. 백그라운드에서 코드베이스를 탐색하여 맥락과 도메인 언어를 파악합니다. 사용자가 버그를 보고하거나, QA를 수행하거나, 대화식으로 이슈를 등록하거나, "QA 세션"을 언급할 때 사용하세요.
대화형 QA 세션: 사용자가 버그나 이슈를 대화식으로 보고하면 에이전트가 GitHub 이슈를 등록합니다. 배경에서 코드베이스를 탐색하여 맥락과 도메인 언어를 파악합니다. 사용자가 버그를 보고하거나, QA를 수행하거나, 대화식으로 이슈를 등록하거나, 'QA 세션'을 언급할 때 사용하세요.
이 스킬은 사용자와 AI 에이전트 간의 대화형 QA 세션을 가능하게 합니다. 사용자가 버그나 이슈를 자연어로 설명하면, 에이전트는 백그라운드에서 관련 코드베이스를 탐색하여 맥락과 도메인별 용어를 이해합니다. 이후 에이전트는 수집된 정보를 바탕으로 구조화된 GitHub 이슈를 자동으로 생성하여 등록합니다. 이는 소프트웨어 개발 과정에서 버그 트래킹과 QA를 보다 직관적이고 효율적으로 만들고자 하는 개발자와 팀에게 유용합니다. 이 스킬은 GitHub Issues 플랫폼과 통합되며, 사용자가 'QA 세션'을 요청하거나 버그 보고와 관련된 키워드를 사용할 때 트리거됩니다.
npx skills add https://github.com/mattpocock/skills/tree/main/skills/qaInstalled? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
대화형 QA 세션에서 사용자가 버그나 이슈를 대화식으로 보고하면, 에이전트가 GitHub 이슈를 등록합니다. 백그라운드에서 코드베이스를 탐색하여 맥락과 도메인 언어를 파악합니다. 사용자가 버그를 보고하거나, QA를 수행하거나, 대화식으로 이슈를 등록하거나, "QA 세션"을 언급할 때 사용하세요.
This repo contains 20 individual skills — each has its own dedicated page.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Compact the current conversation into a handoff document for another agent to pick up.
Implement a piece of work based on a PRD or set of issues.
Implement a specification in code.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Grill me about specs for the workflows I want to build, within this workspace.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.