submit-fix
/submit-fix — Submit Fix PRs and Track
Input
Read .ai/issue-analysis-<issue_number>.md for the issue context.
NOTE: If the analysis artifact say the issue is already fixed or not reproducible, do not proceed with the fix. Report and stop.
Pre-checks — DO NOT SKIP
- Read
.ai/fix-verification-report.md. If the verdict is NOT FIXED, do NOT submit any PRs. Report that the fix has not been verified and stop. - If
.ai/fix-verification-report.mddoes not exist, do NOT submit. Report that verification has not been run and stop. - Also check
.ai/fix-plan-<issue_number>.mdif it exists — if the dev test status is FAILED, do NOT submit.
Only proceed to create PRs if the verification report says FIXED.
Steps
- Identify all repos with changes. Check each repo directory in the workspace for uncommitted or staged changes related to the fix.
- For each changed repo:
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.
18send-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