Get the FREE Ultimate OpenClaw Setup Guide →

Governance

npx machina-cli add skill smith-horn/product-builder-starter/governance --openclaw
Files (1)
SKILL.md
2.1 KB

Governance Skill

Enforces engineering standards from standards.md. Identifies all issues and fixes them immediately -- no deferral, no tickets, no asking for permission. All severities are fixed in the same PR.

Quick Audit

docker exec skillsmith-dev-1 npm run audit:standards

Pre-Commit Checklist

docker exec skillsmith-dev-1 npm run typecheck
docker exec skillsmith-dev-1 npm run lint
docker exec skillsmith-dev-1 npm run format:check
docker exec skillsmith-dev-1 npm test
docker exec skillsmith-dev-1 npm run audit:standards

Sub-Documentation

DocumentContents
code-review-template.mdFull code review report template with field descriptions
retro-template.mdFull retrospective template with completion checklist
edge-function-test.mdEdge Function test scaffold generator with vi.hoisted() pattern

For detailed instructions -- code review workflow, severity guide, zero deferral policy, approach validation rules, retrospective workflow, type safety patterns, and CI failure reference -- see agent-prompt.md.

Source

git clone https://github.com/smith-horn/product-builder-starter/blob/main/skills/governance/SKILL.mdView on GitHub

Overview

Governance enforces engineering standards and code quality policies across the development lifecycle. It requires identifying issues from standards.md and fixing them immediately in the same PR—no deferral, no tickets. It is used during code reviews, before commits, for compliance discussions, quality audits, and retrospectives.

How This Skill Works

Governance runs standard checks and audits (typecheck, lint, format:check, tests, and audit:standards) to surface issues tied to the standards. When issues are detected, all severities must be fixed in the same PR, following the zero-deferral policy, so no follow-up tickets are needed.

When to Use It

  • During code reviews before merging changes
  • When discussing standards or compliance with the team
  • Before commits to ensure code quality gates pass
  • For quality audits against the standards.md policy
  • During retrospectives or when triggering a retro workflow

Quick Start

  1. Step 1: Run the pre-commit checklist (typecheck, lint, format:check, tests).
  2. Step 2: Run the governance audit: standards (docker exec skillsmith-dev-1 npm run audit:standards).
  3. Step 3: Fix all identified issues in the same PR and push the updates.

Best Practices

  • Immediately fix all issues surfaced by governance in the same PR (zero deferral).
  • Run the pre-commit steps: typecheck, lint, format:check, and tests before submitting a PR.
  • Run npm run audit:standards to surface policy violations.
  • Document deviations in the code-review report and keep a clear audit trail.
  • Leverage the provided templates (code-review-template, retro-template) for consistency.

Example Use Cases

  • A code review flags a critical formatting and lint issue; governance fixes all items in the same PR.
  • Before merging a feature, governance runs typecheck, lint, format:check, and tests to ensure standards are met.
  • During a retrospective, governance is invoked to audit adherence to standards and document improvements.
  • An edge function addition triggers edge-function-test scaffolding to validate compliance with testing standards.
  • An audit standards trigger prompts a retro and a complete in-PR remediation of all violations.

Frequently Asked Questions

Add this skill to your agents

Related Skills

Sponsor this space

Reach thousands of developers