agentleFS
gnegreiros-uxgnegreiros-ux/agentica-design-system/.agents/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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    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 21

“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

Cross-tool port of .claude/skills/quality-gate/SKILL.md (Claude Code's native implementation) — see governance/ai-skills-reference.md for the full picture of what Agentica's skills automate, including which of these pipelines are now tool-agnostic CI gates rather than something this skill needs to run itself. This file follows the open Agent Skills format (agentskills.io) so Codex CLI and GitHub Copilot CLI load it automatically from .agents/skills/.

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

Four of these already run as tool-agnostic CI on every push/PR — this skill's job for them is to run the same script locally before proposing a commit, so the CI result is a confirmation, not a surprise. The rest have no script; this skill is the only thing enforcing them, and only if actually invoked.

PipelineCI-enforced (always runs)?Run locally withMandatory
Token consistency✅ tokens-audit.ymlnode scripts/audit-tokens.js --ciYes
Language (English-only)✅ lang-audit.yml (required check)node scripts/audit-language.js --ciYes
Site rebuild✅ site-freshness.ymlnode site/build.js (diff site/dist/ against commit, ignore audit.html)Yes
Commit format✅ commit-lint.yml (PR only)node scripts/check-commit-messages.js <base> <head>Yes
WCAG 2.2—manual checklist (see below)Yes
UX pattern review—see the ux-pattern-review skillYes, for a new component or relevant UX change
Rule / ADR compliance—manual review against decisions/Yes
Missing ADRs—manual — does this change need a new ADR?Yes
Documentation—see the document skillYes
Playwright visual regression (site pages + every Storybook story, ADR-104)✅ CI on push to main; baselines regenerated via workflow_dispatch onlynpx playwright test --project=chromium (after node site/build.js and npm run build-storybook)If change touches components/, tokens/, .storybook/, site/ — list the snapshots expected to change
axe-core⚠️ report mode, non-blockingnpm run axe:allRecommended

Execution sequence

1. git diff --name-only                    → identify modified files
2. Filter triggered pipelines              → per the matrix above
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, GitHub Projects
- 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
- ⏳ Playwright as a PR gate: not yet active

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

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

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.