← all publishers

contextosai

@contextosai source repo

Report this profile Claim this profile

• 19 skills
• 0 followers
• 11 hours ago last updated

1. ▌
   Plan Change · contextosai bundle

   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, design proposal grounded in an existing codebase, or wants to know how a feature or fix should be built before editing begins. Do not use for generic product roadmaps or when the user has asked to implement immediately.
   0
   installs
2. ▌
   Repo Orient · contextosai bundle

   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.
   0
   installs
3. ▌
   Harness Audit · contextosai bundle

   Audit an AI agent's production harness as a release-specific assurance case using repository and runtime evidence. Use for launch-readiness, security, governance, due diligence, control-gap, or post-incident reviews of tool-using, stateful, extensible, long-running, or delegating agents. Produces an impact-tiered launch decision and a focused, evidence-backed fix queue. Do not use for model-only evaluation or as a substitute for authorized runtime testing.
   0
   installs
4. ▌
   Readme Polish · contextosai

   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.
   0
   installs
5. ▌
   Review Change · contextosai bundle

   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.
   0
   installs
6. ▌
   Verify Change · contextosai bundle

   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.
   0
   installs
7. ▌
   Commit Message · contextosai

   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.
   0
   installs
8. ▌
   Pr Description · contextosai

   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.
   0
   installs
9. ▌
   Refactor Safely · contextosai bundle

   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.
   0
   installs
10. ▌
    Triage Incident · contextosai bundle

    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.
    0
    installs
11. ▌
    Contextos Architect · contextosai bundle

    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.
    0
    installs
12. ▌
    Contextos Run Audit · contextosai bundle

    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.
    0
    installs
13. ▌
    Diagnose Root Cause · contextosai bundle

    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 the cause before implementing a fix. Produce an evidence-backed causal explanation and verification plan; do not patch unless the user also asks for a fix.
    0
    installs
14. ▌
    Evolve Schema Safely · contextosai bundle

    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 planning where old and new code or data may coexist. Require explicit expand-migrate-contract sequencing, data invariants, operational bounds, and recovery evidence.
    0
    installs
15. ▌
    Contextos Docs Author · contextosai bundle

    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.
    0
    installs
16. ▌
    Contextos Context Pack · contextosai bundle

    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.
    0
    installs
17. ▌
    Contextos Spec Steward · contextosai bundle

    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.
    0
    installs
18. ▌
    Contextos Contract Sync · contextosai bundle

    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.
    0
    installs
19. ▌
    Contextos Blog Publisher · contextosai bundle

    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.
    0
    installs