ワンクリックでManusで任意のスキルを実行

review-changes

スター2

フォーク0

更新日2026年5月9日 05:05

Review working-tree, branch, or PR changes using graph change detection, blast-radius analysis, affected flows, and test coverage checks.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

afu-it

afu-it/safe-code

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Review Changes

Perform a focused code review of changed code and its blast radius.

Core Rules

Use code-review stance: findings first, ordered by severity, with file and line references where possible.
Start with get_minimal_context_tool(task="review changes").
Run build_or_update_graph_tool() before review if the graph is stale.
Prefer detect_changes_tool(detail_level="minimal") for risk-scored deltas.
Read full source only for changed or high-impact files.
If graph tools are unavailable, review with git diff, rg, and direct file reads.

Scope Modes

No argument: review current working tree against default diff base.
File or function argument: review that target and its graph impact.
Branch argument: review branch diff against main or master.
PR number: inspect the checked-out PR branch or use local git diff if available.

Workflow

Identify diff base from argument or current branch.
Update graph incrementally.
Run detect_changes_tool() for changed files, impacted nodes, risk, and guidance.
Run get_impact_radius_tool() for high-risk changes.
Run get_affected_flows_tool() for critical path changes.
Use query_graph_tool(pattern="tests_for", target=<symbol>) for changed high-risk functions.
Read changed source snippets or full files where needed.
Report only actionable findings.

Output

Findings
- [severity] path:line - issue, impact, fix

Open questions
- ...

Summary
- Risk: <low|medium|high>
- Blast radius: <files/functions/flows>
- Tests checked: <commands or graph coverage>

このリポジトリの他の Skills

同じリポジトリ

safe-code

afu-it/safe-code

Use when asked to run a full repo hygiene pass, full cleanup, or to maintain a repo in one go — and whenever the user invokes /safe-code or any wrapper of it (/skill:safe-code, /skills safe-code, $safe-code, @safe-code, or bare safe-code), including --continue to resume saved work and --save to finalize docs and commit. Also use for first-time project setup, restoring project context or session memory, dead-code audits, or agent-config trust checks.

2026-06-092

codebase-pruner

afu-it/safe-code

Scan an entire codebase to detect and safely remove dead code such as unused functions, orphaned modules, unreferenced exports, stale configs, dead routes, and leftover workflow artifacts. Use when asked to clean up dead code, remove unused code, prune stale files, find orphaned modules, audit codebase bloat, or delete code left behind after a workflow or architecture change.

2026-06-092

safe-refactor-code

afu-it/safe-code

Refactor code safely in small verified slices while keeping repo continuity docs in sync. Uses code-review graph tools for rename previews, impact radius, affected flows, and post-change review when available. Use when an agent is asked to refactor, restructure, clean up, remove or replace code, modernize modules, or do follow-up hygiene in a repo.

2026-06-092

senior-dev

afu-it/safe-code

Senior engineer discipline layer for any coding task. Use when asked to make an AI agent think like a senior/master developer, improve strategy, create task lists, measure twice cut once, keep repositories clean, avoid overengineering, critique strategy adversarially, identify risks, or prevent context-loss mid-task.

2026-06-092

explore-codebase

afu-it/safe-code

Navigate and understand codebase structure using the code-review graph. Use for repo orientation, AGENTS.md authoring, architecture mapping, or finding relevant code.

2026-06-012

build-graph

afu-it/safe-code

Build or update the code review knowledge graph. Use before safe-code audits, refactors, reviews, debugging, or when the graph may be stale.

2026-05-092

name	review-changes
description	Review working-tree, branch, or PR changes using graph change detection, blast-radius analysis, affected flows, and test coverage checks.
argument-hint	[file \| function \| branch \| PR number]

Review Changes

Perform a focused code review of changed code and its blast radius.

Core Rules

Use code-review stance: findings first, ordered by severity, with file and line references where possible.
Start with get_minimal_context_tool(task="review changes").
Run build_or_update_graph_tool() before review if the graph is stale.
Prefer detect_changes_tool(detail_level="minimal") for risk-scored deltas.
Read full source only for changed or high-impact files.
If graph tools are unavailable, review with git diff, rg, and direct file reads.

Scope Modes

No argument: review current working tree against default diff base.
File or function argument: review that target and its graph impact.
Branch argument: review branch diff against main or master.
PR number: inspect the checked-out PR branch or use local git diff if available.

Workflow

Identify diff base from argument or current branch.
Update graph incrementally.
Run detect_changes_tool() for changed files, impacted nodes, risk, and guidance.
Run get_impact_radius_tool() for high-risk changes.
Run get_affected_flows_tool() for critical path changes.
Use query_graph_tool(pattern="tests_for", target=<symbol>) for changed high-risk functions.
Read changed source snippets or full files where needed.
Report only actionable findings.

Output

Findings
- [severity] path:line - issue, impact, fix

Open questions
- ...

Summary
- Risk: <low|medium|high>
- Blast radius: <files/functions/flows>
- Tests checked: <commands or graph coverage>