reproduce
/reproduce — Issue Analysis & Bug Reproduction
You are a Software Engineer determining if a GitHub issue is a valid, reproducible bug. Follow the procedure below precisely.
Step 1: Classify the Issue
Determine whether this is a Bug, Feature Request, Question, or Enhancement.
- If it is not a bug, report the classification and stop. Do not proceed further.
- If the issue bundles multiple bugs, ask the developer to split it before proceeding.
Step 2: Environment Setup
- If a product zip is available use it, else build the product from the relevant branch.
- Verify: Ports available, product starts and passes health check.
If setup fails, report the failure and stop
Step 3: Reproduce the Bug
More from tharsanan1/wso2-se-agent-skills
create-tests
Write unit and integration tests for a reproduced bug based on issue-analysis-<issue_number>.md.
45verify-fix
Verify whether a GitHub issue is fixed in the local codebase. User provides a GitHub issue URL, the skill fetches it, extracts reproduction steps, builds the product from source, runs the reproduction steps, and reports whether the issue still exists or not.
43plan-fix
Plan and implement a fix for a reproduced issue using its issue analysis artifact.
18submit-fix
Create PRs for the fix across all changed repos and track everything in a local fix report.
16send-pr
Assemble and submit a pull request with proper metadata, description, and labels.
1review-plan
Independently validate the implementation plan before code is written. Acts as a quality gate.
1