Menu
Write conventional commit messages and run the repository's pre-push checks before commit, push, or PR title work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user asks to browse, inspect, click, snapshot, or extract evidence from a web page.
Use for demonstrates how a prose browser skill becomes a tested SkillSpec behavior contract. Handles browser handoff and page evidence and external services. Preserves evidence with SkillSpec routes, forbids, dependencies, traces, and token-savings reports
Multiplex SkillSpec post-install setup: inspect skill/repo shape with doctor, map multi-skill and plugin-shaped repositories before fanout import, import existing SKILL.md skills from local folders or public URIs, inspect installed status, install compiled workspaces with entry/support visibility planning, install/update/enable/disable router mode, optionally install/update/enable/disable/delete durable-executor, create specs from observed durable execution workspaces, revise SkillSpec YAML, and prove value before install or release. Use for skillspec, /skillspec, skillspec setup, post install setup, import SKILL.md, import existing skill, port skill, what is the shape of this skill, what is the shape of skill, shape of skill, skill shape and source shape. Use when the task needs to run SkillSpec post-install setup inside the harness prompt, inspect the shape of a skill, skill folder
Multiplex SkillSpec post-install setup: inspect skill/repo shape with doctor, map multi-skill and plugin-shaped repositories before fanout import, import existing SKILL.md skills from local folders or public URIs, inspect installed status, install compiled workspaces with entry/support visibility planning, install/update/enable/disable router mode, optionally install/update/enable/disable/delete durable-executor, create specs from observed durable execution workspaces, revise SkillSpec YAML, and prove value before install or release. Use for skillspec, /skillspec, skillspec setup, post install setup, import SKILL.md, import existing skill, port skill, what is the shape of this skill, what is the shape of skill, shape of skill, skill shape and source shape. Use when the task needs to run SkillSpec post-install setup inside the harness prompt, inspect the shape of a skill, skill folder
Use for every user request when SkillSpec router mode is enabled. First check the local SkillSpec router index, load the selected skill only when route decision is use_skill, and continue with normal agent behavior when the decision is bypass or ambiguous.
Guide construction of MCP servers that expose external services through well-designed, documented, testable tools. Use for mcp-builder, MCP server, Model Context Protocol, build MCP, FastMCP, TypeScript MCP SDK, MCP SDK, MCP tools, MCP evaluations, MCP Inspector, streamable HTTP and stdio transport. Use when the task needs to build an MCP server for an external API or service, design MCP tools, resources, prompts, transport, schemas, pagination, or error handling, implement an MCP server in TypeScript with the MCP SDK, implement an MCP server in Python with FastMCP, review or test MCP server quality and create or run MCP server evaluations. Requires `skillspec decide` before substrate tools or overlapping low-level skills. Preserves evidence with SkillSpec routes, forbids, dependencies, traces, and token-savings reports
| name | generic-commit-convention |
| description | Write conventional commit messages and run the repository's pre-push checks before commit, push, or PR title work. |
Write conventional commit messages and run the repository's pre-push checks before commit, push, or PR title work.
This skill is a thin loader for the colocated skill.spec.yml. The spec is the source of truth for routes, rules, dependencies, imports, resources, recipes, tests, and trace requirements.
Load ./skill.spec.yml from this skill folder before taking task actions.
When the skillspec CLI is available, run:
skillspec decide ./skill.spec.yml --input='<user task>' --trace-dir "${PWD}/.skillspec/traces"
Strip skill invocation prefixes such as /my-skill, $my-skill, or /rote-shell-spec before passing --input.
Preserve the emitted trace run_dir.
When the CLI is available after a trace exists, run skillspec trace align ./skill.spec.yml --decision-trace <run_dir> and report the alignment status with the trace path.
Follow the selected route, matched rules, forbids, elicitations, dependencies, imports, recipes, and closures from skill.spec.yml.
If the CLI is unavailable, read skill.spec.yml directly and apply its rules manually. Do not expand this loader into a second source of truth.
skillspec validate ./skill.spec.yml
skillspec imports check ./skill.spec.yml
skillspec test ./skill.spec.yml
skillspec deps check ./skill.spec.yml
skillspec explain ./skill.spec.yml --input='<user task>' --trace-dir "${PWD}/.skillspec/traces"
skillspec trace align ./skill.spec.yml --decision-trace "${PWD}/.skillspec/traces/<run-id>"
When reporting completion, include the selected route, the SkillSpec trace run_dir, the skillspec trace align status (pass, fail, or unproven), key failed or unproven alignment checks, and the concrete execution evidence ids or files.
message_only: Draft commit message onlypre_push_gate: Run pre-push checkscommit_ready: Prepare commit-ready output