Skip to main content

simplify-reviewed-code

Optionally edit recently reviewed code to reduce unnecessary complexity while preserving behavior and repository conventions. Use only when the user explicitly asks to simplify, clarify, refactor, or polish reviewed changes. Do not trigger as part of PR review, finding validation, or Code Review Rules generation because this skill modifies code.

ソース情報

リポジトリ
neonwatty/codex-pr-review-toolkit
ソースの最終更新活動
2026年8月4日 20:04
検出された SKILL.md の言語
英語
スター
2
フォーク
0

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

ファイルエクスプローラー
2 ファイル

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
simplify-reviewed-code
description
Optionally edit recently reviewed code to reduce unnecessary complexity while preserving behavior and repository conventions. Use only when the user explicitly asks to simplify, clarify, refactor, or polish reviewed changes. Do not trigger as part of PR review, finding validation, or Code Review Rules generation because this skill modifies code.
# Simplify Reviewed Code Keep this workflow separate from review. Announce that it will modify code before editing. ## Workflow 1. Confirm the exact files or diff to simplify and inspect the worktree. Preserve unrelated user changes. 2. Read applicable `AGENTS.md` instructions and identify the repository's verification commands from evidence. 3. Establish a behavioral baseline with focused tests when practical. If the baseline already fails, record that before editing. 4. Simplify only changed or explicitly named code. Favor direct control flow, meaningful names, fewer redundant branches, and removal of abstractions that add no semantic value. 5. Preserve public behavior, error semantics, ordering, concurrency, performance requirements, API/wire shapes, comments that explain non-obvious constraints, and compatibility guarantees. 6. Do not silently fix review findings, broaden scope, alter tests to bless changed behavior, or change repository rules. Ask for separate authorization when simplification reveals a behavioral defect. 7. Re-run the focused baseline plus relevant repository checks. Inspect the final diff for accidental behavior changes. 8. Report edits and verification. If no safe simplification is worthwhile, make no changes and say so. Prefer no edit over a clever or speculative refactor. Never commit, push, or post review comments unless the user separately requests it.
GitHubで見る