From ja
Generate testing documentation from Linear issues and git commits. Use when the user requests test instructions, testing summary, or QA handover documentation for a completed feature or bug fix.
npx claudepluginhub josephanson/claude-plugin --plugin jaThis skill uses the workspace's default tool permissions.
Generate structured testing documentation by analyzing Linear issues and git commits. Produces markdown files with test scenarios, steps, and expected results formatted for QA handover.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Generate structured testing documentation by analyzing Linear issues and git commits. Produces markdown files with test scenarios, steps, and expected results formatted for QA handover.
IMPORTANT: Focus exclusively on QA/blackbox testing. Only include user-facing functionality, UI behavior, and observable outcomes. Exclude implementation details, code verification, component names, or technical internals.
Trigger this skill when users request:
Collect information from multiple sources:
Linear Issue:
Use: mcp__linear-server__get_issue
Extract: title, description, implementation steps, acceptance criteria
Git Commit:
git log -1 --stat # Get commit summary
git show HEAD # Get full diff
Code Changes: Analyze the diff to understand:
Map code changes to QA test scenarios (user-facing only):
Exclude:
Use the template from assets/test-template.md:
Structure:
Scenario Guidelines:
Environment:
Preconditions:
Test Scenarios: Minimum 3-6 scenarios covering:
Standard template for test documentation. Contains the exact structure expected by QA:
# {ISSUE-ID} - Testing Instructions
**Commit:** `{hash}` - {message}
**Issue:** {linear-url}
## Summary
{1-2 sentence overview of changes}
## Changes
- {bullet point list of modifications}
## Test Instructions
### Developer Verification before handover to QA:
- [ ] All scenarios tested & passed
**Environment:** {environment}
**Preconditions, data, feature flags:**
{list preconditions, mock data, feature flags}
---
### 1: {Scenario Title}
**Test steps:**
1. {step}
2. {step}
**Expected results:**
- {expected behavior}
---
### 2: {Scenario Title}
**Test steps:**
1. {step}
**Expected results:**
- {expected behavior}
User request:
"Create test instructions for LSTOCK-469"
Skill execution:
LSTOCK-469git log -1 --stat and git show HEADLSTOCK-469-testing.md