plan-fix
/plan-fix — Plan and Implement a Fix
Input
Read .ai/issue-analysis-<issue_number>.md for the root cause analysis and reproduction details.
NOTE: If the analysis artifact say the issue is already fixed or not reproducible, do not proceed with the fix. Report and stop
Steps
-
Identify the target repo from the issue analysis. If the repo is not already cloned in the current workspace, clone it here.
-
Checkout the correct source version. Before making ANY code changes, you MUST checkout the source repo to the exact version that matches the jars in the product pack. Follow the "Checkout the matching source version" instructions in CLAUDE.md:
- Find the jar version in the product pack's
plugins/directory - Find the matching git tag
- Checkout that tag and create a working branch (
fix/issue-<number>) - Only then proceed to make code changes
- Find the jar version in the product pack's
-
Plan the fix based on the root cause analysis. Keep the change minimal.
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.
42submit-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