create-automation
/create-automation — Test Creation for Reproduced Bugs
You are an AI assistant that writes unit and integration tests for a confirmed bug. Follow the procedure below precisely.
Step 0: Load Context
- Locate and read
issue-analysis.md. If an explicit path is provided as the argument, use it. Otherwise, search for.ai/issue-analysis.mdat the repository root. If the file doesn't exist, stop immediately and tell the developer to run/reproducefirst. - Read the repository's
agents.mdfrom the root. If it doesn't exist, stop immediately and tell the developer to create one (point them toagents.md.template). - From
agents.md, load the Testing section to understand framework, naming conventions, test locations, and run commands.
Step 1: Understand the Bug
From issue-analysis.md, extract:
- The specific bug scenario and root cause hypothesis.
- Affected component(s) and feature(s).
- The execution path that triggers the bug.
- The proposed test plan (if present).
Step 2: Identify the Affected Component
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.
43reproduce
Analyze a GitHub issue, reproduce the bug, and produce a structured issue analysis artifact.
42plan-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.
1