verify-fix
/verify-fix — Bug Fix Verification through Reproduction
Steps
-
Fetch the issue — get the issue details and understand the expected behavior.
-
Check the fix plan — Read
.ai/fix-<issue_number>.mdif it exists. This tells you:- Whether the dev test passed or failed during plan-fix
- What changes were made and in which files
- Any known issues or limitations If the dev test status is FAILED, pay special attention to the "Known Issues" section — the fix may be incomplete.
-
Build and patch the product — Follow the patching instructions in CLAUDE.md:
- Build the changed module(s):
mvn clean install -Dmaven.test.skip=true - Extract a fresh product pack from the zip
- Apply JAR patches to
repository/components/patches/patch9999/ - Apply any template or WAR patches
- Start the server
- Build the changed module(s):
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.
45reproduce
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.
1review-plan
Independently validate the implementation plan before code is written. Acts as a quality gate.
1