Skills address-github-comments
📦

address-github-comments

Content revision r2 Safe ⚙️ External commands

Address GitHub Review Comments Systematically

Pull request feedback can become difficult to track. This skill organizes comments, plans fixes, applies approved changes, and reports completion.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "address-github-comments" from https://skillstore.io/skills/sickn33-address-github-comments.md and its manifest at https://skillstore.io/api/skills/sickn33-address-github-comments/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-address-github-comments.md Signed manifest GET /api/skills/sickn33-address-github-comments/manifest Signed lockfile GET /api/skills/sickn33-address-github-comments/lockfile

Test it

Using "address-github-comments". Inspect comments on the pull request for my current branch.

Expected outcome:

  • Authentication is available.
  • Three review comments were found.
  • Two request code changes, and one asks for clarification.
  • No files were changed.

Using "address-github-comments". Plan fixes for the error handling and test coverage comments.

Expected outcome:

  • Error handling: preserve the original error and add context at the service boundary.
  • Test coverage: add failure-path coverage for rejected requests.
  • Approval is required before editing files.

Using "address-github-comments". Address the approved review comments and summarize the result.

Expected outcome:

  • The two approved changes were applied.
  • Relevant validation completed successfully.
  • The remaining discussion was not modified.
  • A completion response is ready for the pull request.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All nine static alerts are false positives caused by Markdown backticks and fenced command examples, not Ruby or shell backtick execution. The documented GitHub CLI commands use fixed arguments or an explicit pull request placeholder without constructing commands from untrusted input.

1
Files scanned
67
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (9)
SKILL.md:13 SKILL.md:17 SKILL.md:19-21 SKILL.md:21-23 SKILL.md:23-31 SKILL.md:31-33 SKILL.md:33-51 SKILL.md:51-53 SKILL.md:53-58
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-address-github-comments/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-address-github-comments/security.svg)](https://skillstore.io/skills/sickn33-address-github-comments?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-address-github-comments?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-address-github-comments/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-address-github-comments.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). address-github-comments security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-address-github-comments/audits/5

BibTeX citation

@techreport{sickn33-sickn33-address-github-comments-2026, author = {sickn33}, title = {address-github-comments security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-address-github-comments/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "address-github-comments security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-address-github-comments/audits/5" identifiers: - type: other value: "skillstore:sickn33-address-github-comments:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Resolve Author Feedback

Collect reviewer comments, choose priorities, implement approved fixes, and report completion on the pull request.

Track Requested Changes

Convert review threads into a clear checklist and verify that each selected request receives a response.

Coordinate Repository Reviews

Triage many comments before assigning or applying focused changes across an active pull request.

Try These Prompts

Inspect Pull Request Comments 
Check GitHub CLI authentication, then show comments for the current branch pull request. Do not change files.
Create a Review Plan 
List each pull request comment, explain the requested change, and propose a fix. Ask before editing files.
Address Selected Feedback 
Address comments [COMMENT REFERENCES]. Read surrounding code, apply focused changes, run relevant validation, and summarize results.
Manage a Large Review 
Triage all review threads by priority and dependency. Present an execution order, wait for approval, then address the approved group.

Best Practices

  • Read surrounding code before interpreting a reviewer comment.
  • Request user confirmation before addressing a large set of comments.
  • Run relevant validation before reporting a comment as addressed.

Avoid

  • Do not apply every suggestion without checking project context.
  • Do not start changes before confirming GitHub CLI authentication.
  • Do not mark feedback resolved when validation has not completed.

Frequently Asked Questions

Does this skill require GitHub CLI authentication?
Yes. It checks authentication and can guide an interactive login when needed.
Which pull request does it inspect?
The workflow inspects the pull request associated with the current branch.
Will it change files immediately?
It first reviews comments and proposes fixes. Large comment sets require user confirmation before changes.
Can it list individual review threads?
The basic workflow shows pull request comments. Detailed thread listing requires an available custom script or another GitHub CLI query.
Does it run project tests?
The skill requires environment-specific validation, but the documented workflow does not prescribe a specific test command.
Can it post a completion comment?
Yes. It can post a fixed completion message after approved changes are applied.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/address-github-comments

Ref

ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006

Maintenance freshness

7/26/2026

Usage

5 downloads · 103 views

File structure

📄 SKILL.md