AGENT SKILL

coderos

Workspace-native skill for operating, extending, and safe parallel implementation on CoderOS itself. Use when selecting non-overlapping implementation slices, navigating CoderOS governance, scout, work-order, sandbox, and skill-pack seams, and executing safe changes.

License 许可
MIT
最近更新
2026-10-07
Stars
★ 1
Forks
0

01 前言 Front Matter

name
coderos
description
Workspace-native skill for operating, extending, and safe parallel implementation on CoderOS itself. Use when selecting non-overlapping implementation slices, navigating CoderOS governance, scout, work-order, sandbox, and skill-pack seams, and executing safe changes.

02 资源文件 1

03 SKILL.md 正文

CoderOS Workspace Operating Skill

This workspace skill provides the canonical operational model for Antigravity agents working directly on the CoderOS repository (ChristianV997/CoderOS).


1. Quick-Start Repo Inspection Sequence

Before making any edit or starting a work unit on CoderOS, execute this exact 5-step inspection order:

  1. Check Git Status & Active Branch Boundaries

    git status
    git branch -a
    

    Verify current branch, uncommitted changes, and active PR/worktree context.

  2. Verify Active Parallel Assignments & Anti-Collision Boundaries Check active parallel run assignments across team/agent runtimes before claiming file touch-lists:

    • Codex Terminal: Implements skill-pack -> work-order planning bridge (repo_dev_runtime/skill_packs.py, repo_dev_runtime/work_order_plans.py).
    • Codex Remote: Implements improvement decision ledger (repo_dev_runtime/improvement_decision_ledger.py).
    • Grok: Implements routing policy evidence audit (repo_dev_runtime/eval/*, repo_dev_runtime/runtimes/*).
    • Antigravity (Current): Workspace-native operational layers, skills, workflows, operator scaffolding (.agents/*).
  3. Inspect Core Governance & Architecture Docs Read key architectural reference specifications:

    • [docs/AGENT_ORCHESTRATION_ROADMAP.md](file:///C:/Users/HP/Documents/GitHub/CoderOS/docs/AGENT_ORCHESTRATION_ROADMAP.md)
    • [docs/commands-guide.md](file:///C:/Users/HP/Documents/GitHub/CoderOS/docs/commands-guide.md)
    • [docs/work-order-orchestration.md](file:///C:/Users/HP/Documents/GitHub/CoderOS/docs/work-order-orchestration.md)
    • [docs/REPOSITORY_INTELLIGENCE.md](file:///C:/Users/HP/Documents/GitHub/CoderOS/docs/REPOSITORY_INTELLIGENCE.md)
    • [docs/CANDIDATE_SCOUT.md](file:///C:/Users/HP/Documents/GitHub/CoderOS/docs/CANDIDATE_SCOUT.md)
  4. Verify Manifest & Tool Capabilities Run local manifest probing and consumer validation commands to verify environment readiness:

    python -m repo_dev_runtime.cli probe .
    python -m repo_dev_runtime.cli validate-consumers .
    
  5. Validate Test Suite Status Ensure test suite is passing cleanly prior to modifications:

    python -m pytest -q
    

2. Parallel-Run Anti-Collision Rules

To ensure strict safety across concurrent multi-agent and multi-session developments, Antigravity runs must adhere to these hard boundaries:

Protected File Touch-List (DO NOT TOUCH without explicit ownership transition)

  • repo_dev_runtime/skill_packs.py
  • repo_dev_runtime/orchestration.py
  • repo_dev_runtime/contracts/models.py
  • repo_dev_runtime/work_order_plans.py
  • repo_dev_runtime/improvement_decision_ledger.py
  • repo_dev_runtime/cli.py
  • repo_dev_runtime/runtimes/*
  • repo_dev_runtime/eval/*
  • repo_dev_runtime/sandbox.py
  • infra/aws/*
  • scripts/windows/*
  • .github/workflows/*

Execution Boundaries

  1. Single-Slice Focus: Each run must operate on a single, isolated slice.
  2. Additive Workspace Customizations: Prefer workspace-local files inside .agents/ or modular extensions.
  3. No Direct Master/Main Commits: Always work on dedicated feature branches (feat/*, fix/*).
  4. Diff Audit: Perform git diff main...HEAD prior to committing to ensure zero collateral drift.

3. Preferred CoderOS File Entrypoints & Seams

When extending CoderOS capabilities, compose with pre-existing architecture seams rather than inventing parallel runtime abstractions:

Subsystem Primary Entrypoints / Modules Key Seams & Interfaces
Governance & Policy [repo_dev_runtime/governance/](file:///C:/Users/HP/Documents/GitHub/CoderOS/repo_dev_runtime/governance/) RuntimePolicy, authorize(), promotion.json
Scout & Intelligence [repo_dev_runtime/scout/](file:///C:/Users/HP/Documents/GitHub/CoderOS/repo_dev_runtime/scout/), [repo_dev_runtime/intelligence/](file:///C:/Users/HP/Documents/GitHub/CoderOS/repo_dev_runtime/intelligence/) RepositoryIntelligence, FocusedContextBundle, CandidateSource
Personas & Skills [repo_dev_runtime/personas/](file:///C:/Users/HP/Documents/GitHub/CoderOS/repo_dev_runtime/personas/) PersonaRegistry, persona manifests
Work-Order Dispatch [repo_dev_runtime/work_order_orchestrator.py](file:///C:/Users/HP/Documents/GitHub/CoderOS/repo_dev_runtime/work_order_orchestrator.py) WorkOrder, WorkOrderResult, dispatch policy gates
Antigravity Customizations [.agents/](file:///C:/Users/HP/Documents/GitHub/CoderOS/.agents/) Workspace skills, workflows, operator guidelines

4. Seam Composition Principles

  1. Compose Over Invention: Always build on existing RunSpec, QualityReport, WorkOrder, and RepositoryIntelligence contracts. Do not create competing execution kernels.
  2. Dry-Run / Safe Default: All new dispatch paths must default to dry-run or policy-gated authorization (RuntimePolicy.authorize(...)).
  3. Run-State Authority: RunEnvelope (promotion.json) is the single source of truth for run status. External claim stores (scheduler.TaskStateStore) are lock files only.
  4. Offline First: Keep intelligence and scouting operations offline and local-only. Never introduce un-gated network execution or live background daemons.

5. Prompt-Shaping Guidance for Future Antigravity Runs

When writing prompts for future Antigravity sessions on CoderOS, structure requests as follows:

Objective: [Specific additive feature or fix]
Branch: feat/[slice-name]
Allowed Touch-List:
  - [file path 1]
  - [file path 2]
Forbidden Paths:
  - repo_dev_runtime/skill_packs.py
  - repo_dev_runtime/improvement_decision_ledger.py
  - repo_dev_runtime/eval/*
Validation Commands:
  - python -m repo_dev_runtime.cli probe .
  - python -m pytest -q
Expected Artifacts:
  - Code changes & updated tests
  - Clean commit on dedicated branch

04 同仓库更多 Skills