원클릭으로
docs-frontmatter-ontology
// Enforce repository Markdown docs with required YAML frontmatter and ontology_relations, and set up a pre-push hook that blocks pushes when any .md file except AGENTS.md is missing required frontmatter keys.
// Enforce repository Markdown docs with required YAML frontmatter and ontology_relations, and set up a pre-push hook that blocks pushes when any .md file except AGENTS.md is missing required frontmatter keys.
Map a repository's mechanical harness layers: canonical check command, local and CI gates, architecture boundaries, structural rules, behavioral verification, docs ratchets, evidence workflows, and operator-facing surfaces. Use when you need to understand how a repo keeps change safe.
Browser automation for AI agents (Linux/macOS/Windows). Use when the user needs to interact with websites, navigate pages, fill forms, click buttons, take screenshots, extract data, test web apps, or automate browser tasks. Triggers include "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data", "test this web app", "login to a site", or any task requiring programmatic web interaction.
Generate execution-ready implementation plans (PLUS per-task ticket files) from research docs — planning ONLY, no fixing or verifying. North Star is whether a JR developer can execute the work with zero additional context.
Stage all local changes, generate a commit message with branch context, diff stats, and a truncated inline diff versus origin/<branch>, then commit and push with automatic rebase-and-retry when remote is ahead.
| name | docs-frontmatter-ontology |
| description | Enforce repository Markdown docs with required YAML frontmatter and ontology_relations, and set up a pre-push hook that blocks pushes when any .md file except AGENTS.md is missing required frontmatter keys. |
Use this skill when a repo needs consistent documentation shape and enforcement.
For every Markdown file (*.md) except AGENTS.md, require top-of-file YAML frontmatter with these keys:
titlewhen_to_readsummaryontology_relationsontology_relations entries must use this structure:
relationtargetnoteUse this scaffold for new docs:
---
title: "<Document Title>"
when_to_read:
- "When <trigger/scenario #1>."
- "When <trigger/scenario #2>."
summary: "<2-4 sentence practical summary of what this page explains and why it matters>."
ontology_relations:
- relation: "depends_on"
target: "<doc-path-or-concept-id>"
note: "<why this relation exists>"
- relation: "feeds"
target: "<doc-path-or-concept-id>"
note: "<what this doc contributes>"
---
# Purpose
# Scope
# Main content
## Flow / behavior
## Contracts / invariants
## Failure modes
# Related docs
Create scripts/check_markdown_frontmatter.py that:
git ls-files '*.md'AGENTS.md.pre-commit-config.yamlAdd a local hook:
- repo: local
hooks:
- id: markdown-frontmatter-required
name: Require markdown frontmatter (except AGENTS.md)
entry: python3 scripts/check_markdown_frontmatter.py
language: system
files: \.md$
exclude: (^|/)AGENTS\.md$
stages: [pre-push]
pre-commit install --hook-type pre-push
pre-commit run markdown-frontmatter-required --hook-stage pre-push --all-files
.md file except AGENTS.md has required frontmatter keys.pre-commit-config.yaml includes the pre-push hookscripts/check_markdown_frontmatter.py exists and fails correctly on bad files