skills.rest
AAbdulghany
AAbdulghanyCOMMUNITY
Explore all skills by this author →
𝕏@AAbdulghanyyGitHub

approve-design

Record a design.approved marker to gate UI merges after PR design review.

Updated Apr 15, 2026
Search Tags:#workflow#design#ui#merge#pr#approval#gate
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill approve-design-aabdulghany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: approve-design
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/approve-design
Command: npx skills add https://github.com/AAbdulghany/fms --skill approve-design-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill records per-PR design-review approvals to gate UI merges, ensuring only approved design changes proceed.

Core Features & Use Cases

  • Write a per-PR design.approved marker to the approved gate, blocking merges until review is complete.
  • Validate PR state, verify UI-related changes, and ensure the HEAD matches the Rex marker before recording.
  • Support explicit triggers like "PR #X design approved" and respond to design-review questions by recording the confirmation.

Quick Start

Invoke this skill after a designer reviews a specific PR to record the design approval.

Frequently Asked Questions about approve-design

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

FAQPage Schema
How do I enforce design approval before merging UI changes in a pull request?▼

To enforce design approval before merging UI changes, you record a per-PR design.approved marker to gate merges. This blocks merges until a design review is complete, ensuring only explicitly approved front-end changes proceed.

What is a per-PR design approval gate and how does it work?▼

A per-PR design approval gate is a marker written to the repository that blocks UI merges. It works by validating the PR state is OPEN, confirming the marker matches HEAD, and recording a single-line SHA to the marker path.

How do I record a design review approval for a pull request?▼

To record a design review approval for a pull request, invoke an explicit trigger like "PR #X design approved" after a designer reviews the changes. The system then writes the confirmation marker to gate the UI merge.

Can I use a design approval gate for pull requests that only modify back-end code?▼

No, you should not use a design approval gate for pull requests that only modify back-end code. The approval marker is applied only to explicit PR design-approval events for PRs that modify UI assets and front-end files.

Why does my PR design approval marker fail to record?▼

Your PR design approval marker fails to record if the PR state is not OPEN or if the existing marker does not match the current HEAD. The system ensures the PR state is OPEN and confirms the marker matches HEAD before writing.

Related Skills

Explore More Design & Creative Skills→
hadenlabshadenlabs
1

gitlab-validate-mr

Identify CI failures, blockers, and security signals on GitLab merge requests.

Official
Intermediate
me2reshme2resh
489

approve-design

Write per-PR design approval markers with HEAD SHA after validating Rex review.

Community
Intermediate
AnveioAnveio
1

kpi-code-quality

Enforce lint, type safety, test coverage, and build verification in TypeScript/JavaScript projects.

Community
Intermediate
queen-of-codequeen-of-code
8

agent-reviewer

Run CI checks and trace code against an approved Tech Spec.

Community
Advanced