plugin-pr-submit

Manages the pull request submission, CI, and review-fix loop for operator code delivery.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill plugin-pr-submit-wangwindow
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: plugin-pr-submit
Source: https://github.com/WangWindow/CANN-BatchMatMulMaxsum/tree/main/.agents/skills/plugin-pr-submit
Command: npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill plugin-pr-submit-wangwindow

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve? It closes the final gap in an operator development workflow by orchestrating everything from PR submission through CI verification, codecheck fixes, and review comment resolution until the code is accepted upstream. ## Core Features & Use Cases - End-to-end PR lifecycle: Submits the PR after a leftover-issue clearance check, then tracks CI, codecheck, and review feedback in a closed loop. - Async CI state management: Persists a pending_ci waiting state to .cannbot/<ē®—å­å>/state.json and ends the session instead of polling, resuming when the user returns CI results. - Bounded retry and recovery: Limits CI fix cycles to 3 rounds, records per-step progress in state.json, and resumes from checkpoints without rerunning passed steps. - Use Case: After an Ascend C operator passes code review, trigger this plugin to submit the PR, wait for the external CI pipeline, fix codecheck findings from the user-exported report, resolve reviewer comments, and deliver only when CI is fully green. ## Quick Start Ask the assistant to submit the PR for the current operator and drive the CI and review-fix process to upstream delivery.

Frequently Asked Questions about plugin-pr-submit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit a PR and handle CI failures in an automated workflow?ā–¼

Submit the PR after clearing all leftover issues, then record a pending_ci waiting state and end the session instead of polling. When CI results come back, route failures to codecheck or review-fix steps and retrigger CI until all checks pass.

How to fix codecheck issues reported on a pull request?ā–¼

Export the codecheck report from the online system and provide its path in the workspace; the developer agent fixes issues based only on that report, never guessed problem lists. Fixes may touch code, tests, and docs, and must reduce findings to zero.

What are the completion criteria for merging an operator PR upstream?ā–¼

CI must be fully green: for evaluation-set mode all three stages (compile, accuracy, performance) pass with HAP targets met, or for self-built tests run.sh compile and accuracy pass. All review comments must also be closed against the latest code.

How many CI retry rounds are allowed before stopping?ā–¼

The CI trigger-and-fix loop is capped at 3 rounds by default, with counts recorded per step in state.json. Exceeding the limit pauses the workflow, persists a recoverable checkpoint, and asks the user whether to continue, adjust fixes, or stop.

Can the workflow resume after interruption while waiting for CI?ā–¼

Yes. The pending_ci field in state.json marks whether CI is still waiting or results were reported. On recovery the PM resumes from that state, keeping the wait or routing reported results into fix steps or final delivery.