One-click install
npx skills add https://github.com/JeromyJSmith/lattice-platform --skill lattice-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lattice-ci
Source: https://github.com/JeromyJSmith/lattice-platform/tree/main/.agents/skills/lattice-ci
Command: npx skills add https://github.com/JeromyJSmith/lattice-platform --skill lattice-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or drifting GitHub Actions workflows by enforcing that documentation, schema migrations, and API/architecture counts stay consistent before any CI run can proceed.

Core Features & Use Cases

  • Docs-sync gatekeeping: blocks merges when docs drift, forbidden strings appear, or migration/endpoint counts mismatch.
  • Forbidden-string allowlist management: helps you diagnose and safely expand the allowlist when legitimate new terms are introduced.
  • Workflow reliability maintenance: keeps all CI workflows passing on main by aligning workflow changes with the gate logic.

Quick Start

Run bash scripts/pre-commit-docs-check.sh to identify the exact docs-sync failure and then update the referenced sources of truth (and allowlists if needed) in the same commit.

Frequently Asked Questions about lattice-ci

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

FAQPage Schema
How do I prevent GitHub Actions workflow failures from docs drift on main?

GitHub Actions workflow failures from docs drift are prevented by running scripts/pre-commit-docs-check.sh to validate consistency before merging. This gate blocks CI runs when documentation, schema migrations, or API counts mismatch, keeping workflows on main passing.

What is a docs-sync gatekeeping check in CI?

A docs-sync gatekeeping check blocks merges when repository documentation drifts, forbidden strings appear, or migration and endpoint counts mismatch. It enforces that schema, API, and architecture docs stay aligned with workflow changes before CI proceeds.

How do I update migration count and endpoint count metadata to pass CI validation?

Update migration and endpoint counts by modifying meta/SCHEMA.md and meta/API.md in the same commit as your workflow changes. Run scripts/pre-commit-docs-check.sh first to identify exact discrepancies, then align the referenced sources of truth.

How do I diagnose and safely expand a forbidden string allowlist in GitHub Actions?

Diagnose forbidden string failures by running scripts/pre-commit-docs-check.sh, which identifies the blocked terms. Safely expand the allowlist by updating .github/workflows/docs-sync-check.yml when legitimate new terms are introduced in the same commit.

Does workflow validation require the gh CLI to check recent job status on main?

Yes, workflow validation requires the gh CLI to verify recent workflow and job status on main. This helps diagnose failures stemming from reproducibility metadata discrepancies and confirms CI reliability after docs-sync updates.

What's the best way to keep CI docs and counts aligned when modifying GitHub Actions workflows?

Keep CI docs and counts aligned by running scripts/pre-commit-docs-check.sh before committing, then updating meta/SCHEMA.md, meta/API.md, meta/ARCHITECTURE.md, AGENTS.md, and meta/FEATURE_BACKLOG.md so the gate logic remains consistent with your workflow changes.