القائمة
use when leaving an automated comment on a GitHub PR or issue
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use whenever creating or managing git worktrees.
Control Herdr from inside it. Use when running inside Herdr (`HERDR_ENV=1`) to inspect workspaces, tabs, panes, sibling agents, run commands in panes, read output, or wait for state changes via the `herdr` CLI.
Use when debugging, investigating root causes, ambiguous failures, predictions, risk/confidence estimates, or recommendations under uncertainty. Triggers are debug, troubleshoot, root cause, likely, confidence, predict, path forward, next step.
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR, or read/interpret a crit review JSON file. Covers crit comment, crit share, crit unpublish, crit pull, crit push, review file format, and resolution workflow. Not for invoking an interactive review loop — that's the `/crit` command.
Review code changes, a plan, a live page (running dev server), or a local HTML file with crit inline comments
User guide for the local squash-safe `stack` CLI for stacked PR/MR repair on GitHub and GitLab. Use when someone asks how to inspect, track, sync, merge, document, or undo stacked pull requests / merge requests in squash-merge repositories. Prefer this tool over GitHub's `gh stack` command for this workflow.
| name | github-leave-comment |
| description | use when leaving an automated comment on a GitHub PR or issue |
If you are leaving a comment on a GitHub PR or issue on behalf of the user, you MUST end with this exact italic signature on its own final line:
:robot: _OpenCode_
To be clear: there should be a blank line between the end of the comment content and the signature line.