prompt-evaluation-runn…
Use when evaluating prompts, LLM outputs, red-team suites, or model behavior with local eval configs and safe provider/cost…
Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes.
Claude Code
$ npx -y skills add yeaight7/agent-powerups --skill gh-address-comments --agent claude-code
Codex
$ npx skills add yeaight7/agent-powerups --skill gh-address-comments -a codex -y
Cursor
$ npx skills add yeaight7/agent-powerups --skill gh-address-comments -a cursor -y
Gemini CLI
$ npx skills add yeaight7/agent-powerups --skill gh-address-comments -a gemini-cli -y
GitHub Copilot
$ npx skills add yeaight7/agent-powerups --skill gh-address-comments -a github-copilot -y
OpenCode
$ npx skills add yeaight7/agent-powerups --skill gh-address-comments -a opencode -y
Windsurf
$ npx skills add yeaight7/agent-powerups --skill gh-address-comments -a windsurf -y
name: gh-address-comments description: Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes.
Use this skill when the user wants to work through requested changes on a GitHub pull request. Use the GitHub MCP or `gh` CLI for PR metadata and patch context. Treat thread-aware review data as a `gh api graphql` problem — the flat comment surface does not preserve full review-thread state.
Run all `gh` commands with elevated network access. If CLI auth is required, confirm `gh auth status` first and ask the user to authenticate with `gh auth login` if it fails.
1. **Resolve the PR.**
2. **Inspect review context with thread-aware reads.**
3. **Cluster actionable review threads.**
4. **Confirm scope before editing.**
5. **Implement the selected fixes locally.**
6. **Summarize the result.**
If neither the connector nor `gh` can resolve the PR cleanly, tell the user whether the blocker is missing repository scope, missing PR context, or CLI authentication, then ask for the missing repo/PR identifier or a refreshed `gh` login.
# Check auth
gh auth status
# View PR
gh pr view <number> --json number,url,title,state
# List review threads (GraphQL)
gh api graphql -f query='
query($owner:String!, $repo:String!, $pr:Int!) {
repository(owner:$owner, name:$repo) {
pullRequest(number:$pr) {
reviewThreads(first:50) {
nodes {
id
isResolved
isOutdated
comments(first:5) {
nodes { body path line }
}
}
}
}
}
}
' -f owner=OWNER -f repo=REPO -F pr=NUMBERCurated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Use when evaluating prompts, LLM outputs, red-team suites, or model behavior with local eval configs and safe provider/cost…
Use when creating or reviewing red-team eval plugins, attack templates, grader rubrics, safety fixtures, or model-risk test…
Use when designing, running, debugging, or hardening deterministic eval suites for agent skills, prompts, tool workflows, or…
Use when designing tool definitions for a new agent or subagent, an agent shows high retry rates, ambiguous tool invocations, or…
Use when routing a prompt to a local provider CLI for a second opinion, review, or plan -- you are about to call a provider…
Use when starting work in an unfamiliar area of a codebase, spawning a subagent that needs targeted file context, a first search…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.