governance-pack-checklist-validation

Validate .cursor pack mirror symlinks and references for structural integrity.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-pack-checklist-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governance-pack-checklist-validation
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/governance-pack-checklist-validation_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill governance-pack-checklist-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Governance Pack Checklist Validation ensures the mirrors and workspace structure of the .cursor pack are correctly configured with symlinks and free from stale references, preserving operational coherence.

Core Features & Use Cases

  • Validate directory symlinks for the mirrors (.claude/, .continue/, .opencode/, .vscode/).
  • Detect residual or obsolete path references to prevent drift when syncing or reusing the workspace.
  • Provide guidance to repair and re-align the pack before deployment or handoff.

Quick Start

Execute the validation workflow to run a full structural check and report any mismatches in the mirrors.

Frequently Asked Questions about governance-pack-checklist-validation

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

FAQPage Schema
How do I validate .cursor workspace symlinks before syncing across projects?

Validating .cursor workspace symlinks requires checking structural integrity to ensure mirrors like .claude/ and .vscode/ correctly reference their source paths and are free from stale references before syncing.

What is a .cursor pack governance check and when do I need to run it?

A .cursor pack governance check verifies directory symlinks and references to prevent workspace drift. You need to run it as a pre-flight check before syncing projects or after making changes to mirror directories.

How do I detect residual paths and obsolete plan references in .cursor mirror directories?

Detecting residual paths and obsolete plan references involves scanning the .cursor mirror directories to identify and report mismatches, ensuring the workspace remains coherent and free from drift before deployment.

Can I use this validation to repair .claude/ and .continue/ directory symlinks?

Yes, the validation checks directory symlinks for mirrors including .claude/ and .continue/ to identify structural mismatches and provides guidance to repair and re-align the pack for a stable environment.

Why does my .cursor workspace have stale symlink references after syncing?

Stale symlink references occur when mirror directories contain residual or obsolete path references. Validating the .cursor pack structure detects these mismatches to prevent drift when reusing or syncing the workspace.