Assigned by the coordinator of the dependency-update skill, fix one pull request whose review conclusion was "needs changes" within the scope listed in the repository's documents, and push to that pull request's branch. No human is present during the fix.
Prerequisites for running this skill
- The conditions of the execution environment are the same as the model conditions independency-update skill "Checking the execution environment." Check them yourself before starting; if they are not met, change nothing, report the unmet conditions, and finish
- You cannot ask the user questions. Report anything you cannot decide without changing anything
- Follow the coordinator's instructions for the pull request location, clone location, working directory, and label names
- Subagents handling other pull requests in the same repository may be running in parallel. Do not change anything outside the instructed working directory
- Do not merge. The coordinator does that
Check before starting
Fix only when both of the following are met. If either is not met, without changing code, post a comment on the pull request stating that it is out of scope and why, then report and finish. The first line of the comment is # Dependency update fix skipped . The coordinator will not treat a pull request with this comment as a target for fixes until it is reviewed again. Include your Agent name and model name in the comment.
- The repository's rule documents (CLAUDE.md, AGENTS.md, etc.) reference a document listing the places to align when updating dependencies
- All the fixes that the latest review comment required before merge are included in the places listed in that document
Fix
- Check out the pull request's head branch, fix according to the review comments and that document, and add one commit to that branch without creating a new branch
- If during the fix you find that fixes are needed outside the places listed in the document, stop without committing or pushing, post the same out-of-scope comment as in "Check before starting," and report
- Post a comment on the pull request with the places fixed, the commit SHA, and the location of the document followed. The first line is
# Dependency update fix. The coordinator identifies the comment by this line and assembles the re-review instructions. Include your Agent name and model name in the comment. For how to write text that appears on GitHub, follow thekuden:githubskill - If the coordinator has given you a label name, remove the review-request label
- Push last. The reason for pushing after commenting is that if work is interrupted after the push, the commander of the next run cannot tell that this pull request has already been fixed. Re-review after CI finishes is left by the commander to another subagent.
Reporting to the commander
Write briefly.
- The commit SHA, the files fixed, and the location of the document followed
- The URL of the posted comment
- If stopped as out of scope, the reason and the URL of the posted comment
- Points that were ambiguous in the procedure