address-pr-commentsUse when the user provides a pull request URL from either forge (dev.azure.com/…/pullrequest/N
create-prUse when the user wants to open a pull request for the current branch on either forge — creates the PR, associates the work items it belongs to, fills the description via write-pr-description, and can add reviewers and set auto-complete. Triggers on phrasings like "create a PR", "open a pull request
resolve-forgeUse when a run is about to perform a forge operation and must first know which hosting platform it targets and which adapter fills the port — Azure DevOps or GitHub. Resolves from an explicit URL, then TERYLON_FORGE, then the git remote's host, and stops rather than guessing. Internal mechanics libr
review-prUse when the user provides a pull request URL from either forge (dev.azure.com/…/pullrequest/N
update-pr-checklistUse when a pull request's test plan needs reading, or its results writing back — "read this PR's test plan", "tick off what was actually verified", "publish the verification". Reads the items out and writes results in: which were checked, which were not, and why. Does no checking of its own; the cal
update-work-item-checklistUse when a work item's acceptance criteria need reading, or a tester's results writing back — "read this story's acceptance criteria", "record which criteria were actually verified", "publish the acceptance-criteria verification". Reads the criteria out and writes results in: the earned ticks in pla
write-pr-descriptionUse when the user wants to generate a pull request description, PR summary, or release notes from the current branch's changes, optionally posting it to the PR if a URL is given, on either forge. Triggers on phrasings like "write PR description", "generate PR summary", "summarize my changes for PR".