What is uf.address-feedback?

A structured process for handling comments on a GitHub pull request, which is a proposed set of code changes for review. It collects unresolved feedback, assesses it, lets the author triage it, and carries out the chosen fixes.

Use it to review pull-request feedback, group related code changes into commits, run the required review checks, push updates, and reply to comments.

It removes the need to manually gather review comments and decide how to handle them one by one. It also keeps the assessment and execution phases organized when a session is resumed.

How unbound-force/gaze configures Claude Code and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to unbound-force/gaze. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/unbound-force/gaze/main/.opencode/commands/uf.address-feedback.md

Clone the repo

git clone --depth 1 https://github.com/unbound-force/gaze

Made for: Claude Code, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/unbound-force/gaze/uf.address-feedback/github.svg)](https://agentmods.dev/commands/unbound-force/gaze/uf.address-feedback)

Your own site

<a href="https://agentmods.dev/commands/unbound-force/gaze/uf.address-feedback"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.address-feedback/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/unbound-force/gaze/uf.address-feedback"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.address-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 13,282 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.13282
Opus 5.5	$0.00004	$0.05313
Sonnet 5.5	$0.00002	$0.02656
Haiku 4.5	$0.00001	$0.01328

Measured 2d ago against content hash 26d4e5540311, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

uf.address-feedback scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.opencode/commands/uf.address-feedback.md · 1,271 lines

How it starts

The opening of the file, as written. The whole thing — 1,271 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Address Feedback

You are a token-efficient feedback analyst. The user will provide a PR number or you will auto-detect it from the current branch. Fetch all unresolved review feedback from GitHub, classify each item with evidence from project standards, present to the author for triage, then execute decisions as a batch: group related fixes into logical commits, review-council gate, push, reply comments, and artifact production.

The command follows four sequential phases (Ingest → Assess → Triage → Execute). Phases are not independently invocable — run all four in sequence every invocation.

SESSION-RESUME GUARD: If this session has been resumed from compressed context, you MUST:

Re-read this full command template

Call get_progress with command: "uf.address-feedback" to recover checkpoint-based progress state

Check .uf/feedback/pr-<PR_NUMBER>/state.json for cached assessment state

Do NOT infer phase completion or triage decisions from compressed context summaries — only get_progress and state.json are authoritative

Resume from the first incomplete phase

Arguments

PR number (optional): The pull request number to address feedback for (e.g., 42). If omitted, auto-detect the open PR for the current branch.

Argument parsing (before any tool calls): Check the user's message for a PR number argument. If present, set PR_NUMBER to that value immediately. All subsequent steps use <PR_NUMBER> — no auto-detection commands are needed or permitted.

Progress Tracking

At the start of execution, call get_progress with command: "uf.address-feedback" to check for existing progress from a prior session. If progress exists, resume from the first incomplete phase.

After each phase or sub-step completes, call checkpoint with command: "uf.address-feedback" and the step name and data specified at each CHECKPOINT marker below. This progress survives context compression and serves as the authoritative record of progress.

Read the full file on GitHub · 1,271 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago Changed · +26 lines 26d4e5540311
3d ago Changed · +191 lines 19ec49b3cb9d
8d ago Changed · +426 lines 40f0b3cb0aa9
1mo ago Changed 3b2bbba63432
2mo ago Changed · +58 lines 71b1e4e59cbb
2mo ago First seen · 570 lines · 10 tokens per session scan A a7b1ca74b047

Subscribe to this mod's changes

uf.address-feedback is a command published in the GitHub repository unbound-force/gaze (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 13,282 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review

uf.address-feedback next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
uf.address-feedbackunbound-force/gaze	Command	4	yesterday	Apache-2.0	A	10	Claude Code, OpenCode
diff-reviewcoco-research/coco	Command	785	yesterday	Apache-2.0	A	11	Claude Code
review-branchdamusix/atomic-claude	Command	115	4d ago	MIT	A	35	Claude Code
refactorRchGrav/claudebox	Command	1.2k	1mo ago	MIT	A	9	Claude Code
spec-trace-requirementsrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
initazrtydxb/procoder	Command	211	11d ago	Apache-2.0	A	16	Claude Code

gaze: Command for Claude Code