القائمة
Process automated PR review comments systematically. Use this for CodeRabbit, Gemini, GitHub Copilot, Devin, Greptile, and similar bots.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Integrate and use @stll/folio-agents, the framework-neutral LLM tool layer over @stll/folio-core: function-calling tools that read and mutate a .docx document, with every mutation landing as a tracked change or comment pending human review. Load this skill when wiring folio's tools into an agent's tool-use loop (TanStack AI, Vercel AI SDK, raw Anthropic/OpenAI SDKs, or a custom loop), choosing between the headless reviewer bridge and the live-editor-ref bridge, or summarizing what changed between two document versions.
Create a new implementation plan in the repo's planning area.
Shape a feature or problem before implementation. Use this when the request is still fuzzy, when several solutions are possible, or when execution risks outrunning product clarity.
Track down a behavior that used to work and now fails, changed, or regressed. Use this when a bug report points to a recent breakage, especially when the cause is not obvious yet.
Run a security-focused code audit with a generic checklist first, then layer on repo-specific risks.
Review and update third-party dependencies. Use this when asked to upgrade packages, survey new minor or major releases for useful features, assess whether a repository can adopt them, or validate whether a release looks suspicious before bumping it.
| name | rabbit-round |
| description | Process automated PR review comments systematically. Use this for CodeRabbit, Gemini, GitHub Copilot, Devin, Greptile, and similar bots. |
Process automated PR review comments systematically. Use this for CodeRabbit, Gemini, GitHub Copilot, Devin, Greptile, and similar bots.
Get context:
PR_NUMBER=$(gh pr view --json number -q '.number')
gh api user --jq '.login'
git rev-parse HEAD
Fetch review comments from the PR:
gh api repos/{owner}/{repo}/pulls/"$PR_NUMBER"/comments --paginate
Filter for known bot accounts. Do not treat human review comments as bot comments.
Triage each bot comment:
Implement accepted suggestions:
Reply inline to each bot comment:
COMMENT_ID="123456789"
gh api -X POST repos/{owner}/{repo}/pulls/"$PR_NUMBER"/comments/"$COMMENT_ID"/replies \
-f body="[response]"
Good response patterns:
{hash}Never resolve human review threads. For bot threads, resolve only after:
Check nit-level comments too. Small ones still matter if they improve clarity or remove avoidable friction.
Commit and push if you made changes:
fix: address review commentsAccept when the suggestion:
Push back when the suggestion: