A pull-request review helper that collects reviewer comments, analyzes requested changes, applies fixes, and commits the result. A pull request is a proposed code change submitted for review before it is merged.

Use it after reviewers comment on an open pull request to fetch the feedback, fix the code, commit the changes, and post responses.

It keeps review feedback from being scattered across general comments and line-specific comments. It turns the feedback into a follow-up change and response instead of requiring each step manually.

How Fu-Jie/openwebui-extensions configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to Fu-Jie/openwebui-extensions. 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/Fu-Jie/openwebui-extensions/main/.kiro/steering/pr-reviewer.md

Clone the repo

git clone --depth 1 https://github.com/Fu-Jie/openwebui-extensions

Made for: Kiro.

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/instructions/fu-jie/openwebui-extensions/pr-reviewer/github.svg)](https://agentmods.dev/instructions/fu-jie/openwebui-extensions/pr-reviewer)

Your own site

<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/pr-reviewer"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/pr-reviewer/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/instructions/fu-jie/openwebui-extensions/pr-reviewer"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/pr-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 700 This file is loaded in full into every session.

When invoked 700 The same file — it is already loaded in full.

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.00700	$0.00700
Opus 5.5	$0.00280	$0.00280
Sonnet 5.5	$0.00140	$0.00140
Haiku 4.5	$0.00070	$0.00070

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

Security

Grade A, and why

pr-reviewer 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 26d 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.

.kiro/steering/pr-reviewer.md · 82 lines

How it starts

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

PR Reviewer

Overview

This skill automates the response cycle for code review. When a reviewer leaves comments on a Pull Request, this skill fetches all pending feedback, categorizes issues by severity, implements fixes, and submits a follow-up commit with appropriate review response comments.

Prerequisites

An open PR exists with pending review comments
The local branch matches the PR's head branch
gh CLI is authenticated

Workflow

Step 1 — Fetch Review State

Retrieve all review comments and overall review status:

# Get overall review decisions
PAGER=cat GH_PAGER=cat gh pr view <PR-NUMBER> --json reviews,reviewDecision,headRefName \
  --jq '{decision: .reviewDecision, reviews: [.reviews[] | {author: .author.login, state: .state, body: .body}]}'

# Get inline code comments (specific line comments)
PAGER=cat GH_PAGER=cat gh api repos/Fu-Jie/openwebui-extensions/pulls/<PR-NUMBER>/comments \
  --jq '[.[] | {path: .path, line: .line, body: .body, author: .user.login, id: .id}]'

# Get general issue comments
PAGER=cat GH_PAGER=cat gh issue view <PR-NUMBER> --comments --json comments \
  --jq '[.comments[] | {author: .author.login, body: .body}]'

Step 2 — Categorize Review Feedback

Category	Examples	Action
Code Bug	Logic error, incorrect variable	Fix code immediately
Style / Formatting	Indentation, naming convention	Fix code
Documentation	Missing i18n key, wrong version	Fix docs
Design Question	Suggestion to restructure	Discuss with user before implementing
Nitpick / Optional	Minor style preferences	Fix if quick; document if skipped
Blocking	Reviewer explicitly blocks merge	Must fix before proceeding

Step 3 — Implement Fixes

For each accepted fix, apply the change and verify.

Step 4 — Stage and Commit

git add -A
git commit -m "fix(scope): address review feedback"

Step 5 — Push

git push origin $(git branch --show-current)

Read the full file on GitHub · 82 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.

26d ago First seen · 82 lines · 700 tokens per session scan A 64b5ceaa8abf

Subscribe to this mod's changes

pr-reviewer is an instructions file published in the GitHub repository Fu-Jie/openwebui-extensions (333 stars, last pushed 27d ago), licensed MIT. It adds 700 tokens to every session, about $0.0028 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-10-11.

Code review Git and workflow context-engineering excel infographic mindmap openwebui

pr-reviewer next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pr-reviewerFu-Jie/openwebui-extensions	Instructions file	333	27d ago	MIT	A	700	Kiro
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

openwebui-extensions: Instructions file for Kiro