opi-realign

Compare codebase architecture and design between current and target projects.

5|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/OdradekAI/opi --skill opi-realign
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opi-realign
Source: https://github.com/OdradekAI/opi/tree/main/.claude/skills/opi-realign
Command: npx skills add https://github.com/OdradekAI/opi --skill opi-realign

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill compares a current implementation with a target/reference project, providing a detailed review of architecture, feature, design-philosophy, package-boundary, and roadmap realignment.

Core Features & Use Cases

  • Project Comparison: Compare code, architecture, and design between different projects.
  • Audit Drift: Identify and classify drifts in the current implementation compared to the target project.
  • Recommendation: Generate recommendations for realignment and improvements.
  • Use Case: Imagine you have a new project that you want to align with a reference project. Use this Skill to compare the two and get suggestions on how to align your project with the reference.

Quick Start

Run the 'opi-realign' skill and provide the path to the current and target projects, e.g., 'opi-realign --current . --target /path/to/target-project'.

Frequently Asked Questions about opi-realign

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

FAQPage Schema
How do I compare codebase architecture and features between two projects?

To compare codebase architecture and features, you can analyze the current and target projects to identify structural differences, feature gaps, and design philosophy misalignments. The process generates detailed alignment recommendations to sync the current implementation with the reference project.

What is codebase drift analysis and when do I need it?

Codebase drift analysis identifies and classifies divergences in architecture, package boundaries, and design philosophy between a current implementation and a target project. You need it when aligning a new project with a reference codebase to ensure structural and feature consistency.

How do I audit project drift and generate realignment recommendations?

Auditing project drift involves comparing your current codebase against a target reference project to detect architectural and design divergences. The audit yields actionable alignment recommendations, highlighting necessary improvements to match the target's structure and features.

Can I compare projects written in different programming languages?

Comparing projects across different languages requires expertise in the respective project domains and analysis tools. The comparison focuses on architecture, features, and design philosophy rather than syntax, but language-specific expertise is necessary to accurately identify and classify drifts.

What do I need to provide for project comparison and drift analysis?

You need to provide local paths to both the current and target project codebases. Access to analysis tools and expertise in the specific project languages and domains are also required to accurately perform the architecture and feature comparison.

What is the best way to align a new project with a reference codebase?

The best way to align a new project with a reference codebase is to perform a comprehensive comparison of architecture, features, and package boundaries. This identifies specific drifts, allowing you to follow generated realignment recommendations for targeted improvements.