github-address-comments
Github Address Comments
Overview
Use this skill to turn review comments into prioritized, verified fixes and explicit thread closure evidence.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Templates And Assets
- Comment resolution log:
assets/comment-resolution-log-template.md
Shared References
- Reviewer reply patterns:
references/reply-templates.md
Inputs To Gather
- Target PR information.
- Open review comments and thread status.
- Repository validation requirements.
- Scope agreement for this response pass.
Deliverables
- Prioritized comment-action mapping.
- Code changes scoped to accepted comment threads.
- Thread-by-thread responses with verification evidence.
- Deferred-item log for out-of-scope threads.
Workflow
- Confirm
ghauthentication and identify active PR. - Fetch comments using
scripts/fetch_review_threads.py. - Prioritize threads by severity/risk/dependency and log in
assets/comment-resolution-log-template.md. - Implement focused fixes and run relevant validation.
- Reply with concrete change references using
references/reply-templates.md.
Scripts
- Fetch review threads:
python3 scripts/fetch_review_threads.py --repo . --pr <number>
- JSON output for tooling:
python3 scripts/fetch_review_threads.py --repo . --pr <number> --json
Quality Standard
- Every addressed comment maps to code changes or explicit rationale.
- High-severity comments are handled before cosmetic threads.
- Behavior-affecting fixes include verification evidence.
- Responses are specific enough for quick reviewer validation.
Failure Conditions
- Stop when comment intent or scope is ambiguous.
- Stop when requested change conflicts with approved product/architecture decisions.
- Escalate when required context is missing from reviewer discussion.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9