How do I install the Cross Repo Open Diff Reconciliation skill?

Run npx skillmds@latest add grtninja/cross-repo-open-diff-reconciliation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cross Repo Open Diff Reconciliation safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cross Repo Open Diff Reconciliation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cross Repo Open Diff Reconciliation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cross Repo Open Diff Reconciliation?

grtninja (@grtninja) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cross Repo Open Diff Reconciliation by grtninja

Name: Cross Repo Open Diff Reconciliation
Rating: 4.2 (5 reviews)
Author: grtninja

Cross Repo Open Diff Reconciliation

Review recent open diffs across multiple repos, classify repeated release/docs/tests gaps, and route each gap to the right remediation skill. Use when several repos are carrying unreleased work and you need a deterministic audit before patching or curating new skills.

grtninja Updated Sep 10, 2026

File contents

Cross-Repo Open Diff Reconciliation

Use this skill to turn recent multi-repo work into a bounded remediation map.

Workflow

Route the request through $skill-hub.
Run $skills-cross-repo-radar with a bounded lookback window.
Inspect open diffs and changed-file clusters for:
- release-hygiene misses
- docs-lockstep drift
- missing tests
- policy/contract-sensitive changes
- startup/runtime acceptance changes
Classify each repo finding into a small remediation lane.
Route findings to the most specific follow-on skill instead of patching blindly.
Produce a deterministic reconciliation table with:
- repo
- gap category
- severity
- evidence paths
- suggested skill lane
When the user wants new skill curation, cluster repeated findings across repos and propose new skills or upgrades only after the reconciliation map is complete.

Default Gap Routing

release_hygiene_missing -> $skill-arbiter-release-ops
docs_lockstep_missing -> $docs-alignment-lock
tests_missing -> $skill-common-sense-engineering
startup/launcher drift -> $desktop-startup-acceptance
cross-repo contract/policy drift -> $skill-enforcer

Required Evidence

radar JSON output
changed-file samples per repo
category/severity counts
remediation mapping for every flagged repo

Scope Boundary

Use this skill for recent-work reconciliation and remediation routing.

Do not use it for:

deep runtime debugging after the gap is already classified
single-repo PR implementation when a more specific skill already fits
skill admission itself; use $skill-auditor and $skill-arbiter-lockdown-admission after curation

References

references/finding-taxonomy.md

Loopback

If the reconciliation map is incomplete:

capture the missing repo or evidence slice
rerun the radar with narrowed scope or corrected repo list
continue only after every repo has a deterministic finding disposition

---name: cross-repo-open-diff-reconciliationdescription: Review recent open diffs across multiple repos, classify repeated release/docs/tests gaps, and route each gap to the right remediation skill. Use when several repos are carrying unreleased work and you need a deterministic audit before patching or curating new skills.---# Cross-Repo Open Diff ReconciliationUse this skill to turn recent multi-repo work into a bounded remediation map.## Workflow1. Route the request through `$skill-hub`.2. Run `$skills-cross-repo-radar` with a bounded lookback window.3. Inspect open diffs and changed-file clusters for: - release-hygiene misses - docs-lockstep drift - missing tests - policy/contract-sensitive changes - startup/runtime acceptance changes4. Classify each repo finding into a small remediation lane.5. Route findings to the most specific follow-on skill instead of patching blindly.6. Produce a deterministic reconciliation table with: - repo - gap category - severity - evidence paths - suggested skill lane7. When the user wants new skill curation, cluster repeated findings across repos and propose new skills or upgrades only after the reconciliation map is complete.## Default Gap Routing- `release_hygiene_missing` -> `$skill-arbiter-release-ops`- `docs_lockstep_missing` -> `$docs-alignment-lock`- `tests_missing` -> `$skill-common-sense-engineering`- startup/launcher drift -> `$desktop-startup-acceptance`- cross-repo contract/policy drift -> `$skill-enforcer`## Required Evidence- radar JSON output- changed-file samples per repo- category/severity counts- remediation mapping for every flagged repo## Scope BoundaryUse this skill for recent-work reconciliation and remediation routing.Do not use it for:1. deep runtime debugging after the gap is already classified2. single-repo PR implementation when a more specific skill already fits3. skill admission itself; use `$skill-auditor` and `$skill-arbiter-lockdown-admission` after curation## References- `references/finding-taxonomy.md`## LoopbackIf the reconciliation map is incomplete:1. capture the missing repo or evidence slice2. rerun the radar with narrowed scope or corrected repo list3. continue only after every repo has a deterministic finding disposition

Frequently asked questions