rules-normalize

Convert implicit project conventions into explicit GAAI governance rules.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill rules-normalize-petrsimonidesxart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rules-normalize
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/rules-normalize
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill rules-normalize-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert implicit conventions into explicit GAAI governance rules, ensuring rule integrity during creation and modification, and making governance observable and auditable.

Core Features & Use Cases

  • Converts scattered conventions into standardized GAAI rule files under contexts/rules/.
  • Supports bootstrap normalization, new rule creation, and modification workflows with integrity checks.
  • Facilitates deduplication and conflict avoidance by enforcing explicit rule formats.

Quick Start

Run the normalization workflow to convert implicit conventions into explicit governance rules.

Frequently Asked Questions about rules-normalize

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

FAQPage Schema
How do I turn implicit project conventions into explicit governance rules?

Convert implicit conventions into explicit governance rules by applying a normalization workflow that formalizes scattered project practices into standardized GAAI rule files with defined conditions, scope, and enforcement levels.

What is the best way to formalize hidden project conventions for automation and validation?

Formalize hidden project conventions by transforming them into explicit GAAI rule files stored under contexts/rules/, ensuring your governance becomes observable, auditable, and enforced consistently during automation.

When do I need to normalize conventions into explicit rules?

Normalize conventions into explicit rules during project bootstrap when existing conventions exist, when creating a new rule, or when modifying an existing rule to maintain integrity and avoid conflicts.

How do I avoid rule duplication and conflicts when modifying governance conventions?

Avoid rule duplication and conflicts by enforcing an explicit rule format during creation and modification workflows, which standardizes conditions and scope to deduplicate existing conventions.

Does this normalization process require any external dependencies or components?

No external dependencies or components are required. The normalization process operates independently to store standardized rule files under contexts/rules/ with defined conditions and enforcement levels.