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에서 보기