AGENT SKILL

contextos-spec-steward

Change the ContextOS canonical specification and typed reference implementation without semantic drift, conflicting conventions, or unnecessary scope. Use for runtime-model, terminology, compiler, or cross-plane spec changes in the ContextOS repository; not for ordinary site styling.

License 许可
MIT
所属仓库
contextosai/skills
最近更新
2026-10-07
Stars
★ 1
Forks
0

01 前言 Front Matter

name
contextos-spec-steward
description
Change the ContextOS canonical specification and typed reference implementation without semantic drift, conflicting conventions, or unnecessary scope. Use for runtime-model, terminology, compiler, or cross-plane spec changes in the ContextOS repository; not for ordinary site styling.

02 资源文件 2

03 SKILL.md 正文

ContextOS Spec Steward

Make the smallest coherent change to the public spec and its typed reference. New patterns belong in the spec only after validation in a working system; label proposals instead of presenting unproven concepts as canonical.

Establish current truth

  1. Locate the repository root and read the closest AGENTS.md plus repository architecture guidance.
  2. Read the primary spec page, adjacent foundation/implementation pages, current TypeScript types/compiler/scenario, published schemas, and relevant tests.
  3. Search before claiming a primitive or control is absent. Include the foundations docs, implementation docs, typed reference, schemas, and—when the claim is about publication—the actual rendered/live surface if available.
  4. If instructions, docs, code, or schemas disagree, stop and state the conflict. Do not silently blend conventions.

Read references/change-map.md for semantic touch sets and validation routing.

Classify the change

Determine whether the request is:

  • explanatory wording with no contract change;
  • canonical terminology or taxonomy change;
  • type/schema/envelope evolution;
  • compiler behavior change;
  • canonical scenario/example change;
  • new operational pattern or proposed extension.

Write down the invariant being changed and the compatibility expectation before editing. For schema-level work, apply the same compatibility-first sequence across types, producers, schemas, examples, docs, and tests.

Preserve ContextOS invariants

  • The docs are the spec; src/lib/contextos/ is the small deterministic typed reference, not a production runtime.
  • Routing, policy, retry, budget, admission, risk, and threshold decisions are deterministic and fail closed. No random or clock-dependent branching.
  • The five planes retain clear ownership; cross-cutting types are seams, not excuses to collapse boundaries.
  • Native ActionRisk dimensions remain independent. ApprovalMode is only a compatibility projection.
  • Retrieved evidence and memory are data-only; untrusted content never grants authority.
  • Required evidence conflicts remain visible and block commit until resolved by an accountable rule or reviewer.
  • External effects flow through typed tool envelopes, scoped identity, policy, approval where required, postcondition checks, and recoverability semantics.
  • Tests enforce intent. Do not weaken them or widen allowlists to make new content pass.

Edit surgically

Use the coupling map as a maximum coherent set, not a checklist of files to touch. Update only surfaces whose observable contract changes. Keep canonical IDs and examples sourced from the scenario fixture rather than copying stale variants.

When adding a concept, define:

  • plane owner and boundary;
  • inputs/outputs and typed seam;
  • enforcement point;
  • failure mode and fail-closed behavior;
  • evidence, audit, and replay implications;
  • compatibility/migration posture;
  • evaluation and operational ownership.

Call out non-canonical extensions explicitly. Do not add a type solely because prose benefits from a convenient noun.

Verify

Run the narrowest relevant tests first, then typecheck/lint/full tests/build in proportion to the surface. Inspect the diff for accidental terminology changes and verify published routes/assets when touched.

Report changed invariants, coupled surfaces actually updated, compatibility decision, checks run, and anything unverified.

04 同仓库更多 Skills

contextosai
contextosai/skills

template-skill

Replace with a description of what this skill does and when Claude should use it.

★ 1
contextosai
contextosai/skills

verify-change

Design and execute a risk-based verification strategy for a software change, bug fix, refactor, migration, configuration update, or release candidate. Use when Codex needs to prove that a change works, choose proportional tests, investigate whether validation is sufficient, or report what remains unverified. Trace claims to evidence across static checks, focused tests, integration boundaries, and runtime behavior instead of merely running the entire test suite.

★ 1
contextosai
contextosai/skills

triage-incident

Triage an active or recent software production incident by establishing impact, stabilizing the system, preserving evidence, building a timestamped timeline, coordinating hypotheses, and choosing reversible mitigations. Use when users report an outage, severe degradation, security or data-integrity event, broken deployment, elevated errors, or ask for incident command, status assessment, mitigation, or investigation support. Prioritize user harm reduction over root-cause completeness and require explicit authority for production mutations.

★ 1
contextosai
contextosai/skills

review-change

Review a code change for concrete correctness, security, data-integrity, compatibility, concurrency, and operability regressions by reconstructing intent and checking affected invariants and boundary paths. Use for local diffs, commits, branches, patches, or pull requests when the user wants actionable review findings. Report only defects introduced or exposed by the change with precise evidence; do not modify code unless asked to address findings.

★ 1
contextosai
contextosai/skills

repo-orient

Map an unfamiliar software repository from code and configuration. Use when Codex needs to understand a new codebase, locate entry points or ownership boundaries, explain architecture and runtime flow, identify where a change belongs, or prepare for implementation without yet modifying files. Produce an evidence-backed repository map, not a directory listing or README paraphrase.

★ 1
contextosai
contextosai/skills

refactor-safely

Restructure existing code while preserving externally observable behavior through explicit invariants, characterization evidence, small reversible steps, and continuous verification. Use when the user asks to refactor, simplify, extract, reorganize, modularize, deduplicate, split a component, improve architecture, or pay down technical debt without intentionally changing product behavior. Distinguish refactoring from feature work and stop scope drift from hiding inside structural edits.

★ 1