ghm-id-register

Validate and register new SoT IDs with format, uniqueness, and cross-reference checks.

193|9|Updated Jul 10, 2025
One-click install
npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill ghm-id-register
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghm-id-register
Source: https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/ghm-id-register
Command: npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill ghm-id-register

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Validate and register new Source of Truth IDs with cross-reference integrity checks, preventing duplicates and broken references across BR, UJ, API, and CFD domains.

Core Features & Use Cases

  • Validate Format: Ensure IDs follow the [PREFIX]-[3-digit] pattern.
  • Check Uniqueness: Prevent duplicate IDs across SoT files.
  • Verify Cross-Refs: Ensure all referenced IDs exist before registration.
  • Register Entry: Add the validated ID to the appropriate SoT file with a standardized template.

Quick Start

Provide a new ID payload to the ghm-id-register skill to validate, cross-reference, and register it.

Frequently Asked Questions about ghm-id-register

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

FAQPage Schema
How do I validate Source of Truth ID formats before registering them?

To validate SoT IDs, the system enforces the [PREFIX]-[3-digit] format pattern and verifies uniqueness across all SoT files before allowing registration, preventing malformed or duplicate entries.

What is the best way to prevent orphaned references when creating new IDs?

Preventing orphaned references requires cross-reference existence checks before registering any new Source of Truth ID. The system verifies that all referenced IDs exist in their respective SoT files to maintain consistency across domains.

How do I register new IDs across multiple domain SoT files?

Registering new IDs across domains involves providing a new ID payload to validate its format, confirm uniqueness, verify cross-references, and add the entry to the appropriate SoT file using a standardized canonical output template.

Can I use this to check ID uniqueness for BR, UJ, API, and CFD domains?

Yes, uniqueness verification is actively supported for BR, UJ, API, and CFD ID creation workflows. The process scans existing Source of Truth files to prevent duplicate IDs from being registered across any of these domains.

Why does my cross-reference validation fail when registering a new SoT ID?

Cross-reference validation fails when the referenced IDs do not exist in the Source of Truth files. The system enforces cross-reference integrity to prevent broken references, blocking registration until all linked IDs are verified.