skills.rest
petobens
petobensCOMMUNITY
Explore all skills by this author →
GitHub

finish-change

Refines, validates, and finalizes an in-progress code change for commit readiness.

Updated Mar 29, 2024
Search Tags:#git#code review#refactoring#code simplification#diff validation#commit readiness
One-click install
npx skills add https://github.com/petobens/ai-harness --skill finish-change-petobens
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish-change
Source: https://github.com/petobens/ai-harness/tree/main/skills/finish-change
Command: npx skills add https://github.com/petobens/ai-harness --skill finish-change-petobens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In-progress code changes often stall between the first draft and a commit-ready state: review feedback needs validation, the implementation needs simplification, and checks need to run. This Skill brings a change to a defensible stopping point with a clear readiness verdict. ## Core Features & Use Cases - Review Feedback Resolution: Validates findings from pasted reviews or Claude/Codex session logs against the current code, accepting only material fixes and explaining rejections. - Implementation Refinement: Performs one deliberate pass to remove unnecessary abstractions, duplication, and defensive branches while preserving behavior and scope. - Verification and Verdict: Runs applicable formatters, linters, and tests, then declares "Ready to commit" or lists only the remaining blockers. - Use Case: After another agent reviews your pull request, ask the assistant to apply the review, simplify the diff, run the test suite, and confirm the change is ready to commit. ## Quick Start Finish my current uncommitted change by applying the review feedback, simplifying the diff, running the checks, and telling me if it is ready to commit.

Frequently Asked Questions about finish-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I finish a code change after a code review?▼

Provide the review feedback or a Claude/Codex session ID, and the change is validated finding by finding. Accepted findings are implemented, the diff is simplified, checks run, and you receive a clear ready-to-commit verdict.

How to apply review feedback from another AI agent?▼

Paste the review text directly or supply the agent's session ID so its JSONL session log under ~/.claude/projects or ~/.codex/sessions can be read. Each finding is treated as a hypothesis and validated against the current code before being applied.

Does this skill commit or push changes automatically?▼

No. It stops at a readiness verdict and a concise handoff summary. Committing or pushing only happens when you explicitly request it and repository instructions permit it.

When should I not use a finish-change workflow?▼

Do not use it when you only want a review without modifications, or when you have been told not to modify files. It is designed to edit code, run checks, and finalize a change, not to produce review-only output.

What happens if some checks cannot be run?▼

The change can still be declared ready if no material finding remains and the diff stays in scope, but any unavailable check is clearly identified in the verdict. Otherwise it reports not ready and lists only the remaining blockers.

Related Skills

Explore More Software Engineering Skills→
KarlinskySKarlinskyS

requesting-code-review

Gather git change data and dispatch a reviewer subagent with a structured checklist.

Community
Intermediate
flutterflutter
178.7k

shepherd-prs

Automate checking, updating, and landing pull requests in the flutter/flutter repository.

Official
Intermediate
JNZaderJNZader

adversarial-review

Coordinate three-perspective adversarial code reviews on diffs with parallel sub-agents.

Community
Advanced
ntholm86ntholm86
1

kaikaku

Evaluate system architecture for redesign versus incremental improvement.

Community
Advanced