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 查看