跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

luna-chat-coder

Keep repository development reliable from chat by using the sandbox work container first, recovering exact GitHub state, and using bounded Actions missions when normal sandbox or GitHub paths are insufficient.

Osteoporosis · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Osteoporosis/luna-chat-coder --skill luna-chat-coder

技能说明


name: luna-chat-coder description: Keep repository development reliable from chat by using the sandbox work container first, recovering exact GitHub state, and using bounded Actions missions when normal sandbox or GitHub paths are insufficient. license: MIT compatibility: Requires access to durable repository state. The fully specified ChatGPT Web path requires both the GitHub Plugin and the ChatGPT Codex Connector GitHub App for the target repository. GitHub Actions access is required only when an Actions mission is needed. Other Agent Skills hosts may use the core policy only to the extent that equivalent capabilities actually exist. metadata: version: "0.1.5" luna-upstream-version: "0.1.5" luna-upstream-repository: "https://github.com/Osteoporosis/luna-chat-coder" luna-upstream-skill: "https://github.com/Osteoporosis/luna-chat-coder/blob/main/.agents/skills/luna-chat-coder/SKILL.md"

Luna Chat Coder

Luna Chat Coder is a repository-development continuity and fallback policy for ordinary chat. Discover it early, keep it quiet on the normal path, and activate fallback mechanisms only when the normal sandbox or connected GitHub path becomes insufficient.

This policy applies to repository development from a chat surface with a disposable code-execution workspace equivalent to the sandbox work container defined below. Its presence in a repository is not a reason to activate Luna on a persistent/local development machine, an Actions runner, or another unrelated workspace; temporary loss of an otherwise-supported sandbox is handled by degraded remote mode.

Canonical terms

Use these terms consistently:

  • sandbox work container: the isolated, disposable code-execution container attached to the current chat surface. In ChatGPT Web, this means the ChatGPT sandbox work container. Treat it as the primary development workstation, not as the user's computer.
  • durable repository state: exact GitHub state such as a commit, PR head, branch/ref plus its resolved commit SHA, or an immutable repository/Actions artifact.
  • Actions mission: a bounded GitHub Actions execution used when the normal sandbox or connected GitHub path cannot safely or efficiently provide a required capability, exact transport, or execution step. It has explicit inputs, expected source identity, defined outputs, and a terminal lifecycle. It is not an interactive remote shell.
  • degraded remote mode: the exceptional case where the sandbox work container itself cannot sustain the requested engineering work and a sequence of bounded Actions missions temporarily performs edit/build/test execution instead.

Do not use local container, local environment, or bridge for these concepts.

Core invariants

  1. Discover early, activate late. Load this policy before repository work, but do not use Actions merely because the skill is present.
  2. Materialize exact source before editing. When a target GitHub repository is given, resolve the intended commit or PR-head SHA and establish a complete working tree for that exact state inside the sandbox before source edits, builds, tests, or iterative debugging. Inspect surviving sandbox work before replacing it. Prefer normal Git clone/fetch/checkout when the sandbox can reach the repository; otherwise use another exact repository read/archive transport that preserves the required files and identity. Verify the materialized state corresponds to the expected SHA before modifying it.
  3. Sandbox first. Prefer the sandbox work container for source inspection, editing, building, testing, linting, formatting, running services, and iterative debugging once the exact target source has been materialized there.
  4. Inventory before acquiring. Inspect capabilities already present in the sandbox before installing, downloading, or dispatching a mission.
  5. The repository defines the engineering method. Infer required runtimes, services, databases, browsers, compilers, test tools, and versions from repository declarations and task requirements. Do not introduce substitutes or a new methodology on Luna's behalf.
  6. GitHub holds exact durable truth. Chat is useful for intent; conversation reconstruction is not a substitute for exact source when durable source exists. Keep observed repository facts distinct from material assumptions.
  7. Durable handoff is task-owned. Use a branch, PR, issue, commit, or task-owned artifact when losing state would make recovery expensive or ambiguous; keep cheap intermediate reasoning in chat.
  8. Assume concurrent actors. Other chats, agents, CI, or humans may create or move branches, refs, commits, workflows, and artifacts while this task is active. Resolve mutable names to current immutable identity before writes, publication, or cleanup; preserve unfamiliar state and never infer ownership from age or naming alone.
  9. Choose the simplest reliable exact path. Select transport using exactness, payload semantics, integration limits, round trips, and observed reliability. Model-visible text is useful for semantic text; prefer byte-preserving paths for opaque bytes when practical. Transport policy must not alter or suppress repository content.
  10. Verify mission results; diagnose before retrying. Inspect a mission's returned state and expected outputs before relying on them, even when the run reports success. Diagnose failures from logs/results before changing source or repeating an operation; do not guess a root cause from status alone.
  11. The user's host computer is outside the workflow. Do not require direct access to it or ask the user to weaken host isolation merely to unblock ordinary repository development.
  12. Evidence bounds completion claims. Report only operations and checks that actually ran against the relevant state.
  13. Luna owns the safety of mission state it creates. Luna-authored mission machinery—temporary workflows, transport payloads, artifacts, logs, caches, and si
阅读完整来源 ↗