konomitv-to-nx-jikkyo-porter

Port KonomiTV enhancements to NX-Jikkyo via diff review and dead-code removal.

18|Updated Jun 10, 2024
One-click install
npx skills add https://github.com/tsukumijima/NX-Jikkyo --skill konomitv-to-nx-jikkyo-porter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: konomitv-to-nx-jikkyo-porter
Source: https://github.com/tsukumijima/NX-Jikkyo/tree/main/.claude/skills/konomitv-to-nx-jikkyo-porter
Command: npx skills add https://github.com/tsukumijima/NX-Jikkyo --skill konomitv-to-nx-jikkyo-porter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to port KonomiTV enhancements into NX-Jikkyo, ensuring a safe, minimal backport by identifying differences, mitigating dead code, and aligning with NX-Jikkyo's architecture.

Core Features & Use Cases

  • Backport new KonomiTV features into NX-Jikkyo with careful diff-aware adjustments.
  • Detect and remove dead code introduced during porting.
  • Compare diffs between KonomiTV and NX-Jikkyo to understand changes and rationale.

Quick Start

Begin by reviewing KonomiTV changes, map file paths to NX-Jikkyo, and draft a minimal, safe port plan that minimizes differences.

Frequently Asked Questions about konomitv-to-nx-jikkyo-porter

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

FAQPage Schema
How do I backport features from KonomiTV to NX-Jikkyo safely?

To backport KonomiTV features to NX-Jikkyo safely, review the source changes, map file paths to the target architecture, and draft a minimal port plan that mitigates dead code and aligns with removed components.

What is the best way to handle dead code when porting features between projects?

Handling dead code when porting features requires a diff-aware workflow that identifies unused logic introduced during transfer, ensuring safe removal while maintaining compatibility with the target project's architecture.

How does diff analysis help when adapting features to a different project architecture?

Diff analysis helps adapt features by comparing source and target repositories to understand change rationale, identify removed components, and map necessary path adjustments for architectural compatibility.

Can I port enhancements directly without adjusting file paths for the new architecture?

You cannot port enhancements directly without path adaptation; features must be mapped to the target project's file structure to ensure compatibility with its specific architecture and previously removed components.

Why do ported features introduce dead code into the target repository?

Ported features introduce dead code when source enhancements depend on components or logic already removed in the target repository, requiring diff-aware identification and removal to maintain a minimal footprint.