القائمة
Use when writing commit messages, creating PR titles, pushing commits, or creating PRs — ensures conventional commit format and that formatting/linting pass before any push
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | commit-convention |
| description | Use when writing commit messages, creating PR titles, pushing commits, or creating PRs — ensures conventional commit format and that formatting/linting pass before any push |
This project uses Conventional Commits. PR titles are linted by CI and become the squash-merge commit message on main.
Before pushing commits or creating a PR, run both checks and confirm they pass:
cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
If either fails, fix the issues and amend/re-commit before pushing. Only skip these checks if the plan explicitly allows for it.
<type>[optional scope]: <description>
feat(adapter): ...)! after type (e.g., feat!: ...) or add BREAKING CHANGE: footerfeat: add semantic search for skills
fix(grpc): handle timeout on large payloads
ci: add conventional commits PR title linting
feat!: redesign adapter API