菜单
GEODE runtime architecture and repo-shape context. Use for architecture, packaging, release, docs, CI, AgenticLoop, async runtime, and plugin boundary questions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
GEODE CHANGELOG.md management rules. Version releases, change logging, scope determination, format standards. Triggers on "changelog", "release", "version", "릴리스", "변경사항", "버전".
Slack Gateway operations guide. Socket Mode credentials, config.toml bindings, serve restart, receiver debugging, reaction behavior. Triggers on "serve", "gateway", "slack", "바인딩", "binding", "소켓", "socket", "폴러", "poller", "config.toml".
GEODE evidence-first development workflow. Use for feature work, provider/model changes, GUI/computer-use work, PDF/document ingestion, observability/schema/event/state changes, verification planning, GitFlow merge prep, and requests to "follow the workflow" or "scaffold the process".
Publish and verify a released GEODE version across GitHub Release and PyPI/uv, prepare or update the separate Homebrew/core geode-agent formula, and prevent deleted custom-tap paths from returning. Use for Homebrew/core admission, brew formula work, uv/uvx distribution, stable promotions, release repair runs, and public installation-channel audits.
6-lens slop prevention audit — unused imports, dead private fns, duplicate signatures, abandoned TODOs, lint bypass markers, stale refs. Baseline-gated growth check.
Reliable progress monitoring for long-running background tasks (live audits, training, multi-step CI). Covers Monitor + tail buffering pitfalls, polling vs streaming patterns, post-mortem cat/grep, and the Petri × GEODE eval log discovery flow. Triggered by "monitor", "tail -F", "progress", "background", "live audit", "stdbuf", "buffering" keywords.
| name | geode-context |
| visibility | public |
| triggers | geode, harness, agent, runtime, release, packaging, docs, plugin, architecture |
| description | GEODE runtime architecture and repo-shape context. Use for architecture, packaging, release, docs, CI, AgenticLoop, async runtime, and plugin boundary questions. |
Version-agnostic runtime context. For current version and metrics always read
CLAUDE.md or site/src/data/geode/sot.ts — never trust numbers remembered
from this skill.
AgenticLoop(while tool_use).core/ — agent loop, tools, MCP, memory, hooks, wiring, CLI, server, gateway.plugins/ — first-party auxiliary plugins (petri_audit, seed_generation, benchmark_harness).site/ — public Next.js docs/site.AgenticLoop.arun(), tool aexecute(), async provider clients.core/agent/loop/agent_loop.py is the implementation. DEFAULT_MAX_ROUNDS = 0 means unlimited rounds; time budget and model-emitted termination signals (model_action_required, user_clarification_needed) control completion.core/agent/sub_agent.py (SubAgentManager) — max depth 1 (no recursion), session-wide cap 15, global Lane concurrency 50 (core/wiring/container.py).run_bash / delegate_task / computer outright (HEADLESS_DENIED_TOOLS, core/agent/safety.py).core/llm/prompt_assembler.py owns prompt assembly and emits PROMPT_ASSEMBLED.core/agent/system_prompt.py inserts __GEODE_PROMPT_CACHE_BOUNDARY__ between STATIC and DYNAMIC blocks; dynamic context is wrapped in <dynamic_context>.<available_skills> (metadata only); full skill bodies load on demand via the use_skill tool.CHANGELOG.md.ruff check / ruff format --check (core, tests, plugins, scripts), mypy core/ plugins/, lint-imports, pytest -m "not live", geode version smoke.plugins.game_ip imports into core/; Game IP is not the default domain.