issue-createFile a GitHub issue that obeys the title, label, and body conventions of the repository. The skill learns those conventions from the issues that exist, and it does not use a fixed template. It works from a short description or from the current conversation, such as a defect that you just found or a
pr-address-commentsCollect every unresolved review comment on a pull request, triage each one into fix, defer, decline, or already fixed with the author, apply the fixes that the author accepts, and answer each thread. The skill reads all three GitHub comment surfaces, because inline comments, top-level comments, and
pr-create-reviewedOpen a pull request as a draft, examine it with subagents that have no session context, triage the findings with the author, then mark the pull request ready. The subagents get the pull request number, the diff, and their lens, and nothing else: the session that wrote the code holds its own reasons,
pr-createRead the branch diff, write a pull request title and description, and open the pull request with the GitHub CLI. The description states the end state of the diff. It does not narrate the session: no "initially I", no "after review feedback", no changelog of earlier revisions. The skill reads the rep
review-prExamine a GitHub pull request for code quality, security problems, and the rules of the repository. Write every finding in Simplified Technical English (ASD-STE100), in the What, Why, Fix shape, with a file and line citation and a concrete failure scenario. The delivery depends on the author of the