Borrowing it
Nothing to install: this file belongs to takada-at/bq_mcp_server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/takada-at/bq_mcp_server/main/.claude/commands/fix-review-point.mdgit clone --depth 1 https://github.com/takada-at/bq_mcp_serverWrote 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.
[](https://agentmods.dev/commands/takada-at/bq_mcp_server/fix-review-point)<a href="https://agentmods.dev/commands/takada-at/bq_mcp_server/fix-review-point"><img src="https://agentmods.dev/badge/commands/takada-at/bq_mcp_server/fix-review-point/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.
<a href="https://agentmods.dev/commands/takada-at/bq_mcp_server/fix-review-point"><img src="https://agentmods.dev/badge/commands/takada-at/bq_mcp_server/fix-review-point.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00536 |
| Opus 5.5 | $0.00000 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
fix-review-point 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 2mo 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.
What it actually says
Resolveしていないレビューコメントの指摘内容へ対応して下さい。
進め方の手順
- 次項の記載のコマンドを用いて、Resolveしていないレビューコメントを確認する
- Resolveしていないレビューコメントの内容を理解する
- 指摘内容を実現するために必要なタスクを遂行する
- テストとLintを実行し、すべてのテストが通ることを確認する
ghコマンド
以下のコマンドでResolveしていないレビューコメントを取得できます。
OWNER_REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
OWNER=$(echo $OWNER_REPO | cut -d'/' -f1)
REPO=$(echo $OWNER_REPO | cut -d'/' -f2)
PR_NUMBER=$(gh pr view --json number --jq '.number')
gh api graphql -f query="
query {
repository(owner: \"${OWNER}\", name: \"${REPO}\") {
pullRequest(number: ${PR_NUMBER}) {
number
title
url
state
author {
login
}
reviewRequests(first: 20) {
nodes {
requestedReviewer {
... on User {
login
}
}
}
}
reviewThreads(last: 20) {
edges {
node {
isResolved
isOutdated
path
line
comments(last: 20) {
nodes {
author {
login
}
body
url
createdAt
}
}
}
}
}
}
}
}" --jq '
.data.repository.pullRequest as $pr |
{
pr_number: $pr.number,
title: $pr.title,
url: $pr.url,
state: $pr.state,
author: $pr.author.login,
requested_reviewers: [.data.repository.pullRequest.reviewRequests.nodes[].requestedReviewer.login],
unresolved_threads: [
$pr.reviewThreads.edges[] |
select(.node.isResolved == false) |
{
path: .node.path,
line: .node.line,
is_outdated: .node.isOutdated,
comments: [
.node.comments.nodes[] |
{
author: .author.login,
body: .body,
url: .url,
created_at: .createdAt
}
]
}
]
}
'
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.
- 2mo ago First seen · 90 lines · 0 tokens per session scan A c165c4fbcd01
fix-review-point is a command published in the GitHub repository takada-at/bq_mcp_server (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 536 tokens. 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.
Other commands, from other repositories
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.