Menu
Use when you need testing instructions for changes in a branch, before manual QA or creating a PR
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when working with Obsidian vaults, creating/searching/moving notes, or automating note management with the official obsidian CLI, especially with multiline or shell-unsafe content
Use at the end of a Claude Code session to create a comprehensive summary note in Obsidian and add a brief reference to the daily note
Generate architecture diagrams as .excalidraw files from codebase analysis. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, or generate excalidraw files.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
| name | testing-plan-from-history |
| description | Use when you need testing instructions for changes in a branch, before manual QA or creating a PR |
| disable-model-invocation | true |
Generate concise testing instructions by analyzing git history and GitHub PRs for changed files.
digraph testing_plan {
rankdir=TB;
node [shape=box];
diff [label="1. Get branch diff\n(changed files)"];
history [label="2. For each file:\nget git log + PR history"];
extract [label="3. Extract testing patterns\nfrom commits/PRs"];
generate [label="4. Generate concise\ntesting instructions"];
diff -> history -> extract -> generate;
}
# Get the base branch (main or master)
BASE=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "main")
# List changed files
git diff --name-only origin/$BASE...HEAD
For each changed file, gather context:
# Recent commits touching this file (last 10)
git log --oneline -10 -- path/to/file
# PRs that modified this file (if gh cli available)
gh pr list --state merged --search "path/to/file" --limit 5 --json number,title,body
Look for in commit messages and PR descriptions:
Output format - keep it concise:
## Testing Instructions
### Setup
- [ ] Prerequisites or environment setup
### Functional Tests
- [ ] Core functionality to verify
- [ ] Edge cases from bug fix history
### Regression Tests
- [ ] Related features that might be affected
| Source | What to Extract |
|---|---|
| Commit messages | What changed and why |
| PR descriptions | Test plans, context, related issues |
| PR comments | Edge cases reviewers found |
| Issue references | Bug reproduction steps |
| Mistake | Fix |
|---|---|
| Too verbose | Bullet points, not paragraphs |
| Missing setup | Always include prerequisites |
| Only happy path | Include edge cases from history |
| Copying PR verbatim | Synthesize into actionable steps |
## Testing Instructions
### Setup
- [ ] Enable feature flag `new_checkout_flow`
- [ ] Have test account with saved payment method
### Functional Tests
- [ ] Complete checkout with new flow
- [ ] Verify order confirmation email sent
- [ ] Check order appears in admin
### Regression Tests
- [ ] Guest checkout still works (PR #234 context)
- [ ] Discount codes apply correctly
Works well with: