Gh Address CommentsSAFE
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
Overview
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
f10a5237c0bdOBSERVED · 2026-10-26What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: gh-address-comments description: Help 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. metadata: short-description: Address comments in a GitHub PR review --- # PR Comment Handler Guide to find the open PR for the current branch and address its comments with gh CLI. Run all `gh` commands with elevated network access. Prereq: ensure `gh` is authenticated (for example, run `gh auth login` once), then run `gh auth status` with escalated permissions (include workflow/repo scopes) so `gh` commands succeed. If sandboxing blocks `gh auth status`, rerun it with `sandbox_permissions=require_escalated`. ## 1) Inspect comments needing attention - Run scripts/fetch_comments.py which will print out all the comments and review threads on the PR ## 2) Ask the user for clarification - Number all the review threads and comments and provide a short summary of what would be required to apply a fix for it - Ask the user which numbered comments should be addressed ## 3) If user chooses comments - Apply fixes for the selected comments Notes: - If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with `gh auth login`, then retry.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
f10a5237c0bdfull audit observations/trust-audit/skill/composiohq__gh-address-comments.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-26 | f10a5237c0bd | SAFE | B | 89 | first audit |
Questions
What does the gh-address-comments — composiohq/awesome-codex-skills skill do?
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
Is gh-address-comments — composiohq/awesome-codex-skills safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can gh-address-comments — composiohq/awesome-codex-skills access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (f10a5237c0bd), read on 2026-10-26. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/composiohq/gh-address-comments/)
Not your listing, or something out of date? Claim or update your listing.