send-pr
/send-pr — Pull Request Submission
You are an AI assistant assembling and submitting a pull request for a completed bug fix. Follow the procedure below precisely.
Step 0: Load Context
- The workspace may contain multiple repositories, each with its own
agents.mdat its root. Identify the relevant repository and read itsagents.md. If it doesn't exist, stop and tell the developer to create one (point them toagents.md.template). Verify it contains the Contribution Guidelines section. - Read
.ai/code-review-report.md. Verify the verdict is "Ready for PR". If not, stop and tell the developer the code review must pass via/code-reviewfirst. - Read
.ai/issue-analysis.mdfor the issue details. - Read
.ai/implementation-plan.mdfor the fix description. - Read
.ai/plan-review-report.mdfor any implementation notes.
Step 1: Verify Branch
Ensure changes are committed on a properly named branch per agents.md > Branch Naming.
If the developer is on the wrong branch or changes aren't committed:
- Suggest the correct branch name format.
- Ask the developer to commit and push changes before proceeding.
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.
16review-plan
Independently validate the implementation plan before code is written. Acts as a quality gate.
1