gabe-align

Validate code proposals against curated user and project values and scenario coverage.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Brownbull/gabe-suite --skill gabe-align
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gabe-align
Source: https://github.com/Brownbull/gabe-suite/tree/main/skills/gabe-align
Command: npx skills add https://github.com/Brownbull/gabe-suite --skill gabe-align

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align code proposals by validating them against curated user and project values, plus scenario coverage.

Core Features & Use Cases

  • Manual checks across three modes (shallow, standard, deep) to validate proposals before work begins.
  • Automatic checkpoints at commit/PR boundaries that evaluate values and scenario coverage.
  • Command surface including /gabe-align init, /gabe-align status, /gabe-align migrate, and /gabe-align evolve to manage the lifecycle.

Quick Start

Run /gabe-align standard to generate and verify project values and readiness before design and implementation.

Frequently Asked Questions about gabe-align

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

FAQPage Schema
How do I validate code proposals against project values before implementation?

Automatic alignment checkpoints trigger at git commit or pull request boundaries to evaluate code changes against loaded user-level, project-level, and structural values. The system reports PASS, CONCERN, or FAIL to enforce continuous alignment during development.

What is the difference between shallow, standard, and deep alignment checks?

Shallow, standard, and deep alignment checks represent increasing levels of validation depth for code proposals against project values and scenario coverage. Shallow offers quick scans, while deep provides comprehensive validation prior to or during implementation.

How do I set up automated code review checkpoints for git commits?

You set up automated code review checkpoints by initializing the alignment lifecycle management commands to configure project values. Once configured, automatic checkpoints evaluate scenario coverage and values at git commit or PR creation boundaries.

Can I use automated alignment checks across multiple different projects?

Yes, automated alignment checks are usable across projects within the Gabe Suite workflow. You manage the lifecycle per project using initialization, status, migration, and evolution commands to maintain distinct user and project values.

When should I not use automated value alignment for code reviews?

You should avoid automated value alignment when you have not yet curated user-level, project-level, and structural values, as the validation mechanism requires loading these definitions to execute checks and generate accurate PASS, CONCERN, or FAIL results.