메뉴
Use when the user wants to generate manual test cases, QA steps, or test plans based on a git diff of latest commits, branch comparison, or unstaged changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user requests to update, upgrade, or install the latest release of Neovim.
Write a comprehensive, no-placeholder implementation plan as a series of bite-sized tasks, each with exact file paths, real code, TDD steps, and commit instructions. Saves as a GitHub Issue with a [PLAN] prefix. Use after preflight has established what to build.
Present a plan to the user for inline annotation via the ai-review UI. Use when you have a plan ready for human review before executing it. The user will annotate it in the browser; you then revise based on their comments.
Explain the core concepts, library design patterns, system architecture, or host environment internals involved in a plan or git diff. Spawns an isolated subagent to perform the education.
Capture an Architecture Decision Record (ADR) for a significant decision made in the current project. Store in the project's adrs/ folder. Use when the user asks to record a decision, log an ADR, or capture why something was built a certain way. PROACTIVELY suggest capturing an ADR whenever a non-obvious architectural choice is made — technology selection, structural trade-offs, rejected alternatives — especially after a discussion where context and reasoning were developed. A good prompt — "Want me to capture this as an ADR?"
Manage Jack's personal technical reference library at ~/git/references. Use for searching/reading existing references, or adding new ones. Invoke with /jack-references and optional keywords to search, or when the user wants to save a new reference guide. PROACTIVELY suggest saving a new reference whenever the conversation involves figuring out how a library, API, or tool works — especially after debugging, reading docs, or solving a non-obvious integration problem. A good prompt — "Want me to save this as a reference for next time?"
| disable-model-invocation | true |
| name | suggest-manual-tests |
| description | Use when the user wants to generate manual test cases, QA steps, or test plans based on a git diff of latest commits, branch comparison, or unstaged changes. |
Use this skill when the user requests manual test cases or QA verification steps to test recent changes.
Retrieve the Git Diff: Ask the user which git diff they would like to use:
git diff)git diff --cached)git diff origin/main...)git diff HEAD~1)If the user has already specified which diff to use, skip the question and retrieve the diff using the corresponding git command.
Save the output as DIFF_CONTENT.
If the diff is empty, notify the user and ask them to make changes or provide a valid ref.
Analyze the Diff:
Analyze the files and code modified in DIFF_CONTENT. For each modified component, function, endpoint, or page, identify:
Generate Manual Test Cases: Create a structured, succinct list of manual test cases. For each logical/functional change, provide:
TC01: Verify Form Validation on Error).Guidelines:
Present Results: Present the generated manual test cases directly inline in the chat. Do NOT save them to a file or write them to disk.
Refer to sample-test-plan.md for a reference implementation of high-level manual testing scenarios.