Review Implementing
Skill ActiveProcess and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
To systematically process and implement code review feedback, ensuring suggestions are addressed efficiently and accurately within a structured workflow.
Features
- Systematic processing of reviewer notes
- Actionable task creation with TodoWrite
- Guidance for implementing code changes with Edit and Grep
- Handling of diverse feedback types (code, features, docs, tests)
- Validation and communication of implemented changes
Use Cases
- When user provides reviewer comments, PR feedback, or code review notes.
- When user asks to implement suggestions from reviews.
- When user pastes lists of requested changes.
- When user asks to address specific comments on code.
Non-Goals
- Writing code from scratch without prior review feedback.
- Performing code reviews or providing feedback.
- Managing the entire Git workflow beyond implementing changes.
Maintenance
- warning:Commit recencyThe last commit was on March 6, 2026, which is over 3 months ago (today's date for evaluation is May 13, 2026), suggesting potential lack of recent maintenance.
Trust
- warning:Issues AttentionThere are 6 issues opened and 0 issues closed in the last 90 days, indicating a low issue closure rate and potential slow maintainer response.
Installation
First, add the marketplace
/plugin marketplace add mhattingpete/claude-skills-marketplace/plugin install engineering-workflow-plugin@mhattingpete-claude-skillsQuality Score
Trust Signals
Similar Extensions
Moyu (摸鱼)
100과잉 엔지니어링 패턴이 감지되면 자동으로 활성화됩니다: (1) 사용자가 명시적으로 변경을 요청하지 않은 코드나 파일을 수정하는 경우 (2) 요청되지 않은 새로운 추상화 레이어(class, interface, factory, wrapper)를 생성하는 경우 (3) 요청되지 않은 주석, 문서, JSDoc, 타입 어노테이션을 추가하는 경우 (4) 요청되지 않은 새로운 의존성을 도입하는 경우 (5) 최소한의 편집 대신 파일 전체를 다시 작성하는 경우 (6) diff 범위가 사용자의 요청을 명백히 초과하는 경우 (7) 사용자가 "너무 많아", "거기는 건드리지 마", "X만 변경해", "간단하게", "그만" 등의 신호를 보내는 경우 (8) 발생할 수 없는 시나리오에 대한 에러 처리, 유효성 검사, 방어적 코드를 추가하는 경우 (9) 요청되지 않은 테스트, 설정 스캐폴딩, 문서를 생성하는 경우
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Github
100Use gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
ClawSweeper Skill
100Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.