스킬 검색.../

Heavy Approval Governor | Skills Pool

스킬 파일

Heavy Approval Governor

Enforces Heavy-tier approval gates, question lock, and visual approval rules before implementation. Use when tasks may be Heavy, when approving drastic loop changes, or when validating compliance with LOOP_TIERING.

farcenterextremist0 스타2026. 3. 31.

직업
카테고리: 코드 품질

스킬 내용

Purpose

Prevent unauthorized Heavy changes and keep approvals explicit, traceable, and safe.

Primary references:

docs/automation/LOOP_TIERING.md
docs/automation/HEAVY_IDEAS_FAVORITES.md
docs/automation/IMPROVEMENT_LOOP_ROUTINE.md
docs/automation/FRONTEND_CHANGE_AUTOMATION_GATE.md

Trigger

Use this skill when requests mention:

"heavy task"
"drastic change"
"approval gate"
"question lock"
"approve 100% implement"

Workflow

Classify scope
- Confirm whether task is Light/Medium/Heavy by current tier definitions.
Enforce gate
- For Heavy: stop and ask for approval options.

관련 스킬

빠른 설치

Heavy Approval Governor

npx skills add farcenterextremist/Out-of-route-buddy

Skill 다운로드 저장소 열기

작성자: farcenterextremist
스타: 0
업데이트: 2026. 3. 31.
직업

이 페이지의 내용

Apply question lock and visual approval clause where required.

Validate authority

For frontend/UI changes, enforce Master Loop-only rule and frontend gate.

Record evidence

Capture approval wording, selected items, and any exclusions in summary/ledger.

Proceed safely

Implement only approved scope; defer everything else with explicit next steps.

Output checklist

Tier classification recorded
Heavy approval request shown (if needed)
Question lock + visual clause applied (if needed)
Frontend authority/gate validated (if UI touched)
Approval evidence written to summary/ledger

Guardrails

Never treat missing approval as implicit approval.
Keep Heavy execution bounded to exact approved items.
If approval is ambiguous, ask before implementing.

02

Trigger

04Output checklist

준법감시인

Openclaw Release Maintainer

Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

Verify

Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

Flow

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

자동화 도구

Fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

Hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

microsoft184.0k

Add Policy

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

microsoft184.0k

준법감시인