minimax-submodule-parity

Audit PMOVES submodule overlays against upstream and generate parity_report.md.

6|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/POWERFULMOVES/PMOVES.AI --skill minimax-submodule-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minimax-submodule-parity
Source: https://github.com/POWERFULMOVES/PMOVES.AI/tree/main/.kilocode/skills/minimax-submodule-parity
Command: npx skills add https://github.com/POWERFULMOVES/PMOVES.AI --skill minimax-submodule-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PMOVES overlays can diverge from upstream submodule capabilities, leading to integration drift and unstable deployments. This skill provides a structured audit and parity-reporting workflow to verify overlays against upstream.

Core Features & Use Cases

  • Audit submodule configurations via .gitmodules and current overlay branches.
  • Compare local overlays against upstream and generate parity reports.
  • Validate submodule interfaces against PMOVES integration contracts and surface gaps.
  • Produce actionable mapping reports to guide updates and gitlinks.

Quick Start

Run a parity audit for the PMOVES HiRAG submodule and review the generated parity_report.md.

Frequently Asked Questions about minimax-submodule-parity

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

FAQPage Schema
How do I audit git submodule overlays against upstream branches?

To audit submodule overlays against upstream, parse the .gitmodules file, compare local overlay branches to upstream capabilities, and validate integration contracts to generate a structured parity report.

Why do my submodule overlays diverge from upstream capabilities?

Submodule overlays diverge from upstream capabilities due to integration drift over time. Comparing your overlay branches against upstream configurations and validating integration contracts surfaces these alignment gaps.

What is a submodule parity report and when do I need it?

A submodule parity report maps overlay alignment against upstream capabilities. You need it when validating integration contracts, auditing overlay alignment, or producing parity outputs during deployments to prevent unstable releases.

Can I validate submodule integration contracts using a .gitmodules file?

Yes, you can validate submodule integration contracts by parsing the .gitmodules file and current overlay branches. The process compares local overlays against upstream to surface interface gaps and produce actionable mapping reports.

What is the best way to generate a parity report for submodule release validation?

The best way to generate a parity report for release validation is to run a structured audit that parses .gitmodules, compares overlay branches to upstream, and validates integration contracts, outputting a parity_report.md file.

How do I fix integration drift after comparing local submodules to upstream?

To fix integration drift after comparing local submodules to upstream, use the generated actionable mapping reports to guide submodule updates and correct gitlinks, ensuring your overlays regain parity with upstream capabilities.