claude

contextos-stewardship

Maintain the ContextOS specification, runtime contracts, documentation, and editorial publishing surfaces without semantic drift.

1 on GitHubMITupdated 1 month ago
/

Plugin contextos-stewardship from marketplace contextosai-skills in contextosai/skills. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (19)

  • commit-message

    Write a clear, conventional git commit message from staged changes. Use when the user asks to commit, write a commit message, or describe what changed.

  • contextos-architect

    Design or assess an agent system using ContextOS's five-plane runtime model, canonical contracts, and staged adoption path. Use for architecture, migration, or thin-slice design; do not use merely to edit ContextOS documentation or schemas.

  • contextos-blog-publisher

    Create, revise, or package a ContextOS blog post with editorial positioning, accurate runtime terminology, frontmatter, category routing, read-next links, social metadata, and optional cover art. Use for blog publishing; not for canonical spec pages.

  • contextos-context-pack

    Author, review, or evolve a ContextOS Context Pack and its compiler fixtures, policies, tools, decisions, evidence gates, memory rules, and evaluator targets. Use when the requested artifact is a Context Pack or compiled-context scenario, not for generic prompt writing.

  • contextos-contract-sync

    Add or evolve ContextOS runtime contracts across TypeScript types, JSON Schemas, canonical examples, documentation, and drift tests. Use for RunContext, ContextPack, CompiledContext, ToolEnvelope, DecisionRecord, ReplayPacket, or delegation changes; not for prose-only edits.

  • contextos-docs-author

    Create or revise ContextOS MDX documentation while preserving frontmatter, foundation templates, navigation, component registration, canonical examples, URL stability, and spec/reference alignment. Use for docs pages, not blog posts or contract implementation alone.

  • contextos-run-audit

    Audit a ContextOS proof-carrying run using RunContext, CompiledContext, ToolEnvelope, DecisionRecord, trace, scorecard, and ReplayPacket artifacts. Use for incident review, launch evidence, or record completeness; do not use for a whole-repository harness maturity audit.

  • 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.

  • diagnose-root-cause

    Diagnose software failures through reproduction, boundary localization, competing hypotheses, and discriminating experiments. Use when Codex is asked to investigate a bug, flaky test, crash, incorrect result, performance regression, production symptom, or unexplained behavior and should determine th

  • evolve-schema-safely

    Design, implement, or review compatible and reversible database, event, API payload, configuration, or persisted-data schema evolution. Use for migrations, column or field changes, backfills, constraint changes, data transformations, serialization upgrades, zero-downtime deploys, or rollback plannin

  • harness-audit

    Audit an AI agent harness using repository and runtime evidence. Use for release readiness, security assurance, harness-change evaluation, or incident review of tool-using, stateful, extensible, or delegating agents. Produces scoped findings, evidence gaps, and a prioritized closure plan; makes a la

  • plan-change

    Produce an implementation-ready plan for a software change by inspecting the actual repository, tracing affected execution paths, resolving material design decisions, and defining verification and rollout evidence. Use when the user asks for an implementation plan, technical approach, task breakdown

  • pr-description

    Draft a pull request title and description from the commits and diff on the current branch. Use when the user asks to open a PR, write a PR description, or summarize a branch's changes for review.

  • readme-polish

    Improve a project's README for clarity, structure, and completeness without changing its meaning. Use when the user asks to clean up, polish, or improve a README or project documentation.

  • 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, improv

  • 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. Produc

  • 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 actiona

  • 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

  • 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 un

View source on GitHub

More from contextosai/skills

All 4 plugins →

Design ContextOS-aligned agent runtimes, author governed Context Packs, and audit proof-carrying runs against current contract invariants.

19 skills

1

A collection of example skills demonstrating the SKILL.md pattern, including commit messages, PR descriptions, and README polishing.

19 skills

1

Evidence-based triage, release, change, and incident review for AI agent harnesses. Traces authority and effects, challenges permission boundaries and evaluation integrity, and produces scoped findings, closure evidence, and launch decisions when requested.

19 skills

1

Maintain contextos-stewardship?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins4 plugins