gh-address-comments
OfficialHelp address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
What we know about this skill
Publisher
openai
Matched to the vendor's own GitHub organisation.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned openai/skills at 49f948faa9.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 49f948faa9
- Scanned
- 4 files, 271 lines
About this skill
What it does
This skill uses the gh command-line interface to respond to comments on a GitHub pull request associated with the current branch. It verifies authentication with GitHub and prompts the user to log in if necessary. The tool allows for direct interaction with code review processes, enabling efficient feedback loops within development workflows.
When to use it
- Responding to reviewer questions or concerns raised in a GitHub PR comment.
- Acknowledging receipt of feedback on a pull request.
- Providing clarifications or additional context related to specific changes in the PR.
- Marking comments as resolved after addressing the associated issues.
Key capabilities
- Authenticates with GitHub using
gh. - Prompts user authentication if not already logged in.
- Utilizes the
ghCLI for interacting with GitHub pull requests. - Addresses comments directly within the GitHub PR interface.
Example prompts
- "Respond to the comment from @user about the function 'calculate_average'."
- "Mark the comment regarding the performance optimization as resolved."
- “Address the question in the latest review comment.”
Tips & gotchas
- Ensure you have the
ghCLI installed and configured on your system. - The skill requires authentication with GitHub; be prepared to log in if prompted.