Run any Skill in Manus with one click

harness-contract-change

Stars4,986

Forks758

UpdatedMarch 26, 2026 at 12:24

Modifies the repository's agent contract including AGENTS.md, docs index, manifests, validation scripts, and contributor-facing harness wrappers. Use when updating agent documentation, changing repo manifests, editing validation scripts, modifying CI/workflow classification, or updating contributor-facing guides like README.md, CONTRIBUTING.md, or the PR template.

Installation

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.

Run Skill in Manus

Source

vllm-project

vllm-project/semantic-router

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	harness-contract-change
category	primary
description	Modifies the repository's agent contract including AGENTS.md, docs index, manifests, validation scripts, and contributor-facing harness wrappers. Use when updating agent documentation, changing repo manifests, editing validation scripts, modifying CI/workflow classification, or updating contributor-facing guides like README.md, CONTRIBUTING.md, or the PR template.

Harness Contract Change

Trigger

Change AGENTS.md, docs/agent/*, tools/agent/*, tools/make/agent.mk, or harness-facing CI/workflow classification
Change contributor-facing wrappers that explain the harness, such as README.md, CONTRIBUTING.md, or the PR template

Required Surfaces

harness_docs

Conditional Surfaces

harness_exec
contributor_interface
ci_e2e

Stop Conditions

The edit would create a second conflicting source of truth instead of updating the canonical one
The rule change cannot be enforced or validated in the same change

Workflow

Read agent README, governance docs, and execution-plan guidance for current contract state
Modify agent contract docs, manifests, validation scripts, or contributor wrappers
Run make agent-validate to check alignment between docs and manifests
Run make agent-ci-gate CHANGED_FILES="..." to verify all surfaces pass
Record any durable code/spec divergence as indexed debt entries

Gotchas

Do not add a prose-only harness rule when the same invariant can be enforced in manifests, scripts, or CI.
When routing, validation, or contributor workflow changes, update the executable layer and the human-readable layer in the same patch.

Must Read

Standard Commands

make agent-validate
make agent-scorecard
make agent-report ENV=cpu CHANGED_FILES="..."
make agent-ci-gate CHANGED_FILES="..."

Acceptance

Harness docs, manifests, scripts, and contributor wrappers remain aligned
The change improves discoverability, source-of-truth clarity, or mechanical enforcement of the harness
Any durable code/spec divergence discovered during the harness change is recorded in the matching indexed debt entry instead of being left only in PR text

More from this repository

same repository

openclaw-vsr-bridge

vllm-project/semantic-router

Install vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR.

2026-07-135.0k

vllm-semantic-router-harness

vllm-project/semantic-router

Bridges native skill discovery into the vLLM Semantic Router repository harness, routing tasks through the canonical agent-report flow, repo-local skill registry, and validation commands. Use when starting any task inside the vLLM Semantic Router repository to resolve the correct primary skill, read canonical docs, and run harness validation.

2026-05-305.0k

config-platform-change

vllm-project/semantic-router

Synchronizes config representations across router config, Python CLI schema, and dashboard config UI. Use when adding or changing a config concept that spans those surfaces or addressing config representation debt before Kubernetes-facing translation.

2026-05-305.0k

k8s-platform-change

vllm-project/semantic-router

Modifies Kubernetes-facing operator, CRD, deployment-profile, or DSL translation behavior for semantic-router platform integration. Use when changing operator APIs or controllers, deployment stack manifests, profile-owned platform wiring, or router-to-Kubernetes translation layers.

2026-05-305.0k

maintainer-issue-pr-management

vllm-project/semantic-router

Manages GitHub issue and pull-request lifecycle including creation, updates, triage labelling, and closeout metadata using canonical templates and repository taxonomy. Use when a maintainer asks to create, update, close, or triage GitHub issues or PRs, or when issue creation requires codebase analysis for scope, labels, or acceptance criteria.

2026-05-305.0k

maintainer-release-ops

vllm-project/semantic-router

Maintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, create milestone issues, sync GitHub issue or PR state, generate a daily review brief, or manage stale PRs and backlog routing.

2026-05-305.0k

name	harness-contract-change
category	primary
description	Modifies the repository's agent contract including AGENTS.md, docs index, manifests, validation scripts, and contributor-facing harness wrappers. Use when updating agent documentation, changing repo manifests, editing validation scripts, modifying CI/workflow classification, or updating contributor-facing guides like README.md, CONTRIBUTING.md, or the PR template.

Harness Contract Change

Trigger

Change AGENTS.md, docs/agent/*, tools/agent/*, tools/make/agent.mk, or harness-facing CI/workflow classification
Change contributor-facing wrappers that explain the harness, such as README.md, CONTRIBUTING.md, or the PR template

Required Surfaces

harness_docs

Conditional Surfaces

harness_exec
contributor_interface
ci_e2e

Stop Conditions

The edit would create a second conflicting source of truth instead of updating the canonical one
The rule change cannot be enforced or validated in the same change

Workflow

Read agent README, governance docs, and execution-plan guidance for current contract state
Modify agent contract docs, manifests, validation scripts, or contributor wrappers
Run make agent-validate to check alignment between docs and manifests
Run make agent-ci-gate CHANGED_FILES="..." to verify all surfaces pass
Record any durable code/spec divergence as indexed debt entries

Gotchas

Do not add a prose-only harness rule when the same invariant can be enforced in manifests, scripts, or CI.
When routing, validation, or contributor workflow changes, update the executable layer and the human-readable layer in the same patch.

Must Read

Standard Commands

make agent-validate
make agent-scorecard
make agent-report ENV=cpu CHANGED_FILES="..."
make agent-ci-gate CHANGED_FILES="..."

Acceptance

Harness docs, manifests, scripts, and contributor wrappers remain aligned
The change improves discoverability, source-of-truth clarity, or mechanical enforcement of the harness
Any durable code/spec divergence discovered during the harness change is recorded in the matching indexed debt entry instead of being left only in PR text