skills.rest
oliverhuynh
oliverhuynhCOMMUNITY
Explore all skills by this author →
GitHub

repo-governance

Establish repository governance rules, task status recording, and UX→UI→FE development order.

Updated Aug 27, 2026
Search Tags:#workflow#ui#frontend#repository#governance#ux#task-status
One-click install
npx skills add https://github.com/oliverhuynh/codex-master --skill repo-governance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-governance
Source: https://github.com/oliverhuynh/codex-master/tree/main/skills/repo-governance
Command: npx skills add https://github.com/oliverhuynh/codex-master --skill repo-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clear rules for repository governance, clarifies task status tracking, and enforces a consistent UX→UI→FE development order to reduce cross-team misalignment.

Core Features & Use Cases

  • Cross-cutting governance rules to standardize terminology and escalation paths.
  • Task status recording and updating guidance, including the required task.md format.
  • Implementation placement guidance: stage work under tasks/NNN-*/output/ before integration.
  • Explicit admin actions and change-approval requirements to minimize scope creep.

Quick Start

Apply the repo-governance rules to a repository and update a sample task to In Progress.

Frequently Asked Questions about repo-governance

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

FAQPage Schema
How do I enforce a consistent UX to UI to frontend development order in my repository?▼

To enforce a consistent development order, this Skill establishes cross-cutting repository governance rules that standardize the UX to UI to FE workflow sequence, reducing cross-team misalignment and ensuring terminology consistency across design and frontend tasks.

What is the correct format for recording task status in a repository?▼

Recording task status requires maintaining a task.md file with explicit status updates. This Skill specifies the required task.md format and provides guidance on updating task states to ensure transparent tracking throughout the software development lifecycle.

How should I stage frontend and design changes before integrating them into the main branch?▼

You should stage changes under the tasks/NNN-*/output/ directory before integration. This Skill provides implementation placement guidance to ensure work is properly isolated and reviewed prior to merging into the main codebase.

How can I minimize scope creep and manage admin actions in a software development workflow?▼

To minimize scope creep, this Skill defines explicit admin actions and change-approval requirements. It establishes clear escalation paths and governance rules to control administrative tasks and prevent unauthorized project modifications.

Does this repository governance approach require any specific dependencies or external components?▼

No, this repository governance approach does not require any external dependencies or components. It operates as a standalone set of rules and conventions that can be applied directly to standardize workflows across design, frontend, and admin tasks.

Related Skills

Explore More Product & Management Skills→
gileckgileck

setup-agent-tasks

Set up agent tasks for a child project using task-cli with JSON configs.

Community
Intermediate
divad12divad12
25

ship

Save progress, commit changes, and merge into main in one action.

Community
Intermediate
Euraika-LabsEuraika-Labs
14

team-ui

Orchestrate multi-role UI workflows for game projects from specification to polish.

Official
Advanced
MichealWayneMichealWayne
207

select-package

Classifies requests by runtime and domain to select the fe-tools package directory before coding.

Community
Intermediate