rewrite

Generates a new target-stack application from an existing source application through gated, cluster-based code translation.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill rewrite-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rewrite
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/rewrite
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill rewrite-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Migrating an application to a different language or framework (e.g., Java to .NET, Express to Angular) is risky: teams lose behavioral fidelity, underestimate effort, and discover integration surprises late. This Skill manages out-of-place, generative code translation where the source app stays read-only and a new target application is authored in a separate folder, with every stage measured and gated rather than assumed. ## Core Features & Use Cases - Posture resolution and options analysis: Detects the source stack, resolves the migration posture from stack distance (port, re-architecture, or rewrite-from-spec), and presents 2-3 target options compared across assurance ceiling, effort, and dated TCO, each with its own target-space dependency DAG. - Gated design and generation: Authors seven target design documents behind an APPROVE DESIGN gate, then generates code per cluster in isolated git worktrees, with design-quality and implementation gates judged independently. - Measured assurance: Computes a per-cluster Behavioral Assurance Level (BAL, weakest-link on mechanical counts) and a whole-target Enterprise-Readiness Level (ERL), enforced through merge and completion gates with hard blocks for high-risk clusters. - Use Case: A team needs to translate a .NET Framework monolith into a Spring Boot backend with an Angular frontend. The Skill verifies integrations, presents costed target options, generates the new application cluster by cluster, and blocks any cluster whose behavioral assurance falls below the agreed floor. ## Quick Start Ask the assistant to rewrite the application in the current repository from its existing stack to a named target stack, for example: rewrite this Express API to a .NET 8 minimal API in a new target folder.

Frequently Asked Questions about rewrite

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

FAQPage Schema
How do I migrate an application from one framework to another?

Run the rewrite flow: it detects the source stack, resolves the migration posture from stack distance, presents target options with effort and TCO, then generates the new application cluster by cluster in a separate folder. The source code stays read-only throughout.

What is the difference between port and re-architecture in a code rewrite?

Port applies only when source and target share both language and framework, allowing structure-preserving translation. Any language or framework change forces re-architecture, where the target structure is redesigned rather than copied from the source.

Can I bring my own target architecture design to a rewrite?

Yes, a BYO design (diagram or design document) is accepted as an alternative to generated options. It is ingested, assessed on assurance, effort, and TCO, and judged with the same critic scrutiny as generated options before being accepted.

How is behavioral correctness measured during a code translation?

Each cluster receives a Behavioral Assurance Level computed as the weakest link of oracle availability, verified behavior coverage, and test pass rates, using mechanical counts. A cluster with no runnable oracle is capped at level C regardless of coverage.

What happens if a generated cluster fails the quality gates?

A cluster at provisional BAL D cannot merge, and a high-risk B-series cluster below the assurance floor is hard-blocked at completion, requiring a named approver and written reason. Design-quality failures trigger regeneration of the flagged units.

When should I not use a generative rewrite approach?

Avoid it when source and target share the same language and framework, where an in-place upgrade is cheaper, or when no behavioral inventory exists and assurance requirements are high, since the absence of a runnable oracle caps achievable assurance at level C or D.