pattern-alignment

Compare new code implementations against project contract patterns and conventions.

2|Updated May 24, 2026
One-click install
npx skills add https://github.com/CivicActions/ai-runbook-jh --skill pattern-alignment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattern-alignment
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/pattern-alignment
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill pattern-alignment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of codebase drift by ensuring that new implementations adhere to established project patterns, conventions, and architectural standards rather than introducing inconsistent or legacy approaches.

Core Features & Use Cases

  • Pattern Verification: Automatically compares new code against canonical examples defined in the project contract.
  • Divergence Detection: Identifies structural, naming, and stylistic deviations, providing clear feedback on whether they are intentional or accidental.
  • Legacy Flagging: Highlights when a developer is replicating outdated patterns, offering modern alternatives based on the project's current browser baseline.

Quick Start

Use the pattern-alignment skill to check if my current implementation of the user profile component follows our existing codebase patterns.

Frequently Asked Questions about pattern-alignment

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

FAQPage Schema
How do I check if my new code follows existing project architecture and conventions?

To check code consistency, you analyze new implementations against established project patterns and conventions defined in the project contract, identifying canonical examples and flagging structural or stylistic divergences.

What is the best way to prevent codebase drift during feature development?

Preventing codebase drift requires pattern verification, automatically comparing new code against canonical examples to ensure implementations adhere to established architectural standards rather than introducing inconsistent approaches.

How do I identify outdated or legacy patterns during a code review?

To identify legacy patterns during a code review, you flag replications of outdated approaches and highlight structural deviations, offering modern alternatives based on the project's current browser baseline.

Do I need a project contract to perform architectural consistency checks?

Yes, performing architectural consistency checks requires access to the project contract and codebase to identify canonical examples and flag divergences in new software engineering implementations.

Can I detect naming and stylistic deviations in new feature implementations?

Yes, you can detect naming and stylistic deviations through divergence detection, which identifies structural inconsistencies and provides clear feedback on whether they are intentional or accidental.

When should I avoid using automated pattern verification for code reviews?

You should avoid automated pattern verification when lacking an established project contract or canonical codebase examples, as the process requires these to accurately identify divergences and flag legacy approaches.