Menu
Fetches unresolved comments from the specified PR and applies the fixes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Triage a Forecast-in-a-Box team meeting transcript against the GitHub board โ propose new high-level issues, status changes, and PR links, then apply them only after the user approves the full plan.
Analyze the changes compared to latest releases. Helps determine which releases should be triggered, and provides release notes for them.
Analyzes the whole codebase, asserts whether it is aligned with the high level guidelines, identifies transgressions, proposes fixes.
Analyzes the changes made in the current branch to the codebase in `backend/`, determines how those changes impact the `frontend/` codebase, and writes minimalistic fixes to resolve compatibility issues.
| name | adapt-pr-comments |
| description | Fetches unresolved comments from the specified PR and applies the fixes. |
| argument-hint | <PR-number> |
When the user invokes this skill, they will supply a PR number which you should use when calling github API.
The recent changes you did were pushed to the repo, under the pull request #, and reviewed by the user.
Fetch all currently unresolved comments from the repository. If you fail to fetch any, report it and wait for next input.
If you have successfully fetched the comments, think critically about them -- some of the comments may be posed as questions, some may not be informed. If even a single comments raises a doubts on your side -- the comment is not clear, the user perhaps didnt realize there is a side-effect, the comment suggest an approach you tried and decided not to pursue, do not make any code changes, but instead describe your thoughts, and wait for next input.
If, on the other hand, everything will seem clear and spot on, proceed with applying relevant fixes to the codebase.
Once just val passes, make a commit, dont push, describe your changes in brief to the user, then wait for next input.
