agentleFS
gnegreiros-uxgnegreiros-ux/agentica-design-system/.claude/skills/quality-gate/SKILL.md

quality-gate

Skill2 starsChanged 46 days agoApache-2.0View on GitHub

Pre-commit orchestrator for the Agentica repository — runs every active quality pipeline (tokens, WCAG, UX patterns, ADR compliance, docs, site rebuild, commit format) in order, generates one impact report, and waits for explicit human approval before any commit. Use before every commit, however small — this is the full gate; the lighter post-change-pipeline skill covers only impact analysis.

46 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use deploy.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this quality gate after every modification, regardless of size:

    line 24
  2. Very specific:

    Create .claude/skills/pipelines/[name].md with the standard format (see ../pipelines/style-dictionary.md as a stub example)

    line 133
  3. Distinctive:

    Add a line to the "Available pipelines" table above

    line 134
  4. Distinctive:

    Create an ADR if the pipeline represents a significant architectural decision

    line 136

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: quality-gate

Pre-commit orchestrator. Runs all active pipelines in order, generates an impact report, waits for human approval before any commit. Type: skill Logical path: .claude/skills/quality-gate/SKILL.md Read before: AGENTS.md, governance/rules/post-change-pipeline.md Relations: .claude/skills/pipelines/, decisions/ADR-029-quality-gate-pre-commit.md


Absolute rule

No commit until all mandatory blocks have been run and approved by the human.


Trigger

Run this quality gate after every modification, regardless of size:

  • Modification of a token (primitive, semantic, component)
  • Modification of a component or a site page
  • Addition or modification of a rule, an ADR, a guideline
  • Configuration change (build, Style Dictionary, etc.)

Available pipelines

PipelineFileStatusMandatory
Token consistency../pipelines/tokens-audit.md✅ ActiveYes
Language (English-only)../pipelines/language-audit.md✅ ActiveYes
WCAG 2.2../pipelines/wcag.md✅ ActiveYes
UX pattern review../pipelines/ux-patterns.md✅ ActiveYes (new component + relevant UX change)
Rule / ADR compliance../pipelines/adr-conformity.md✅ ActiveYes
Missing ADRs../pipelines/adr-triggers.md✅ ActiveYes
Documentation../pipelines/docs.md✅ ActiveYes
Site rebuild../pipelines/site.md✅ ActiveYes
Commit../pipelines/commit.md✅ ActiveYes
Style Dictionary../pipelines/style-dictionary.md🔜 PlannedOnce active
Storybook../pipelines/storybook.md🔜 PlannedOnce active
axe-core../pipelines/axe-core.md🔜 PlannedOnce active
Playwright (visual regression, incl. Storybook stories)../pipelines/playwright.md✅ ActiveYes (change to components/, tokens/, .storybook/, site/) — flag expected snapshot changes
Backlog reconciliation../pipelines/backlog.md✅ ActiveYes — at PR completion, not per-commit

Execution sequence

1. git diff --name-only                    → identify modified files
2. Filter triggered pipelines              → per the matrix in each pipeline
3. Run each active pipeline                → generate report items
4. Present the full report                 → checklist format below
5. Wait for explicit approval               → "Yes, go ahead" or requested changes
6. Execute the approved tasks              → in order: tokens → site → docs → commit
7. Commit in a single coherent commit      → conventional commits, no --no-verify

Report format

## Quality Gate — approval required

### Modified files
- [list of files from git diff]

### 1. Token consistency
- [ ] No hardcoded value (hex, px, hardcoded font-family)
- [ ] All referenced tokens exist
- [ ] No orphaned token created

### 2. WCAG 2.2
- [ ] Normal text contrast ≥ 4.5:1
- [ ] Large text contrast ≥ 3:1
- [ ] Focus visible on all interactive elements
- [ ] Touch targets ≥ 24×24px (WCAG 2.5.8)
- [ ] No animation without prefers-reduced-motion

### 2b. UX pattern review (if a component was created/modified — otherwise "N/A")
- [ ] Suggested patterns presented to the human with direct links
- [ ] Human decision recorded (✅/❌ per pattern)
- [ ] 6 surfaces documented: guideline, code, story, site, ADR, log
- or: N/A — no component created and no relevant UX modification

### 3. Rule / ADR compliance
- [ ] Active ADR #XX respected: [specific rule]
- [ ] ...

### 4. Missing ADRs
- [ ] [Decision X] → ADR-0XX to create: [proposed title]
- or: No new ADR required

### 5. Documentation
- [ ] guidelines/[section].md updated
- [ ] Work reflected in GitHub Projects (status, domain) — see ADR-069
- [ ] decisions/README.md updated (if new ADR)
- [ ] FR/EN bilingual parity verified
- [ ] Site rebuild: node site/build.js

### 6. Planned pipelines (non-blocking)
- ⏳ Style Dictionary: not yet active
- ⏳ Storybook: not yet active

### 7. Commit
- [ ] Format: type(scope): short description
- [ ] A single coherent commit
- [ ] No /Users/... path in committed files

### 8. Backlog reconciliation (at PR completion only — see `../pipelines/backlog.md`)
- [ ] Related GitHub Projects tickets read back and their `Status` matches what
      the PR's full diff actually shipped
- [ ] `Dépendance` text on any touched ticket still makes sense (no "Bloque" a <!-- lang-audit-ignore: verbatim GitHub Projects field/status names -->
      now-`Terminé` target while still open itself) <!-- lang-audit-ignore: verbatim GitHub Projects field/status names -->
- [ ] New work discovered but untracked → ticket created (Status/Domaine/Date, ADR-069)
- or: N/A — mid-PR commit, not yet at merge time

### Points of attention
- [escalations, special Principal Designer approvals]

Adding a new pipeline

  1. Create .claude/skills/pipelines/[name].md with the standard format (see ../pipelines/style-dictionary.md as a stub example)
  2. Add a line to the "Available pipelines" table above
  3. Set the status to ✅ Active once the pipeline is operational
  4. Create an ADR if the pipeline represents a significant architectural decision

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.