project-consolidate-cursor

Audit .cursor packs across six checks and generate a compliance report.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill project-consolidate-cursor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-consolidate-cursor
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/project-consolidate-cursor_V1.1.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill project-consolidate-cursor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditoria o pack .cursor para identificar desvios de convenções, validar conformidade e gerar um relatório de auditoria sem modificar conteúdos.

Core Features & Use Cases

  • Verifica versionamento de arquivos e pastas, links Markdown, estrutura canônica e nomenclatura de arquivos.
  • Detecta se o /init foi executado e se o autostart está configurado, oferecendo recomendações de melhoria.
  • Use Case: Você solicita "consolidar cursor" para obter um relatório de governança do pack .cursor.

Quick Start

Execute a auditoria de 6 checks no pack .cursor para gerar um relatório de conformidade.

Frequently Asked Questions about project-consolidate-cursor

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

FAQPage Schema
How do I audit my .cursor pack for convention deviations and compliance issues?

A .cursor pack audit validates init execution, autostart configuration, versioning, canonical structure, naming conventions, and Markdown links. It generates a read-only compliance report that identifies deviations and provides recommendations for improvement.

Can I validate broken links and file naming conventions without modifying my project files?

Yes, this read-only auditing workflow performs safe, non-destructive validation of broken Markdown links and naming conventions. It surfaces deviations and generates a compliance report without modifying your original project files.

Why do I need to verify if /init was executed and autostart is configured in my .cursor pack?

Verifying /init execution and autostart configuration ensures proper pack initialization and workflow governance. The audit detects these settings, confirms correct setup, and provides recommendations for structural improvement.

What is the best way to check the canonical structure and versioning of a .cursor pack?

The best way to check canonical structure and versioning is running a comprehensive six-check audit. It validates files and folders against expected conventions, identifies structural deviations, and outputs a detailed conformance report for governance.

Does the .cursor pack audit workflow require any external dependencies or components?

No external dependencies or components are required to run the .cursor pack audit workflow. It operates independently as a read-only validation tool to surface deviations and generate compliance reports safely within your environment.