proposer-guide
Use source and execution tools to investigate a supplied program and check a proposed change against evidence.
- License 许可
- MIT
- 所属仓库
- HKUDS/AgentPilot
- 最近更新
- 2026-11-12
- Stars
- ★ 8.0k
- Forks
- 944
01 前言 Front Matter
- name
- proposer-guide
- description
- Use source and execution tools to investigate a supplied program and check a proposed change against evidence.
03 SKILL.md 正文
Read source and execution evidence
Read missing code before relying on a name, diagram or docstring. Follow related_implementations into callees when a claim depends on their behavior.
Use paths and record references from the supplied directories:
- list_sources() browses code; read(path="src/main.py", line=40) reads file lines.
- search(query="text") searches source and opens a unique match when possible; use scope="trace" to search executions.
- list_cases(view="tasks") reads task requirements independently of outcomes. list_cases() browses executions; read_trace(ref="<record reference>") opens one.
- check_trace(ref, start, end, name) optionally counts and orders recorded tool requests in an event interval; omit name to include all tools. It checks facts, not whether the proposed change would improve results.
- Follow returned next calls to continue, open calls to inspect a match, and expand calls to recover omitted text. No cursor conversion is needed.
Inspect relevant attempts before connecting their observations. Successful repeats help compare behavior, but neither success nor failure proves a cause. Executor explanations and printed self-verdicts are claims. A recorded tool result may mix terminal output and harness feedback; keep an unknown origin unknown. Keep early ideas provisional: check whether the change already exists, would trigger, or would still accept the recorded failure. Check whether its new action would occur in time to affect that failure. When counterevidence rules out the idea, revise the mechanism or narrow its applicability.
Independent reads may share a response; wait for results when the next action depends on them.
04 同仓库更多 Skills
agentpilot
Set up AgentPilot and use its single entry to prepare missing inputs and run configured RSI experiments. Use when the user requests AgentPilot installation or work with AgentPilot.
remember
Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.
skill-discovery
Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.
delegate-task
Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.
write-special-chars-ts-check
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.
write-special-chars-readback
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of /tmp helper scripts.