Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Modify code based on GitHub PR review comments and create a local commit using gh + git. Use when the user asks to "follow PR comments", "fix review comments...
Modify code based on GitHub PR review comments and create a local commit using gh + git. Use when the user asks to "follow PR comments", "fix review comments...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this workflow for PR-comment-driven changes.
PR URL (preferred), e.g. https://github.com/owner/repo/pull/123 Optional scope from user (e.g. only one comment, all unresolved comments)
Parse owner/repo and PR number from URL. Inspect PR summary: gh pr view <url> --json number,title,headRefName,baseRefName,files,reviews,reviewDecision Fetch inline review comments: gh api repos/<owner>/<repo>/pulls/<number>/comments Extract actionable items from comment bodies. Ensure local repo exists in workspace: If missing: git clone git@github.com:<owner>/<repo>.git Checkout PR branch in local repo: gh pr checkout <number> Open affected files and implement requested changes exactly. Validate changed files quickly (lint/test only if needed or requested). Commit: git add <files> git commit -m "<clear message>" Report back with: What changed Commit hash Branch name Push only if user asks/approves: git push
Prefer minimal diffs that address reviewer intent directly. Do not silently alter unrelated code. If a comment is ambiguous, ask one focused clarification question. If no local repo exists, clone first instead of failing. Include failed attempts in the final operation log when user asks for traceability.
# PR meta gh pr view <url> --json number,title,headRefName,baseRefName,files,reviews,reviewDecision # Inline review comments gh api repos/<owner>/<repo>/pulls/<number>/comments # Checkout PR branch (inside repo) gh pr checkout <number> # Status and commit git status --short git add <files> git commit -m "chore: address PR review comments"
PR: <url> Addressed comments: <n> Changed files: <path>: <summary> Commit: <hash> Branch: <branch> Pushed: yes/no
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.