skills.rest
rmethodm
rmethodmCOMMUNITY
Explore all skills by this author →
GitHub

port-code-with-approval

Ports code from another project through staged per-item user approval.

Updated May 26, 2026
Search Tags:#code review#refactoring#migration#approval workflow#code porting#feature import
One-click install
npx skills add https://github.com/rmethodm/resumegen --skill port-code-with-approval-rmethodm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: port-code-with-approval
Source: https://github.com/rmethodm/resumegen/tree/main/.agents/skills/port-code-with-approval
Command: npx skills add https://github.com/rmethodm/resumegen --skill port-code-with-approval-rmethodm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When importing code or features from another project, bulk copy-ins often introduce conflicts, unwanted features, and unreviewed changes. This Skill enforces a staged workflow where each ported item is reviewed and approved before moving on. ## Core Features & Use Cases - Ordered Porting Plan: Surveys the source project first and produces an ordered list of files, features, or logical chunks to port before any implementation begins. - Per-Item Approval Gates: Implements one item at a time, pausing for explicit user approval and revisions before continuing to the next. - Conflict Flagging: Identifies source code that conflicts with existing project conventions or previously removed features before porting it. - Use Case: When asked to pull in an entire feature set from a legacy project, the Skill still ports item by item, treating "everything" as scope rather than permission to skip review. ## Quick Start Ask the assistant to port the authentication module from the old project into this repository using staged per-item approval.

Frequently Asked Questions about port-code-with-approval

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

FAQPage Schema
How do I port code from another project without breaking my current one?▼

Port code in staged steps: first survey the source and list the items to port, then implement one item at a time with explicit approval before continuing. This prevents bulk copy-ins from silently introducing conflicts or unwanted features.

How to migrate features between repositories incrementally?▼

Break the migration into an ordered list of files, features, or logical chunks, then work through them sequentially. Pause after each item for review and revision so every change is confirmed before the next begins.

Can I tell it to port everything at once?▼

No. A request to port everything defines the scope of work, not permission to skip review. The workflow still implements each item individually and waits for explicit approval before moving to the next one.

What happens when ported code conflicts with existing conventions?▼

Conflicting code is flagged before it is ported rather than copied in silently. This includes clashes with project conventions or features that were previously removed, giving you a chance to decide how to handle each conflict.

When is staged per-item porting not the right approach?▼

It is less suitable for trivial single-file copies or greenfield imports with no existing conventions to protect. In those cases a direct copy with a single review pass is usually sufficient.

Related Skills

Explore More Software Engineering Skills→
vmitsarasvmitsaras

repository-feature-plan

Plans how a new feature fits into an existing repository's architecture, tests, and documentation.

Community
Intermediate
luigiinredluigiinred
1

dev-workflow-prepare-commit

Review staged changes, run linters and tests, and generate conventional commit messages.

Community
Advanced
dotnetdotnet
18.2k

code-review

Review dotnet/runtime code changes for correctness, performance, and conventions.

Official
Advanced
woxiangyangzhimaowoxiangyangzhimao
3

batch

Execute sequential code changes with checkpoints and rollback.

Community
Advanced