返回提示词目录第 1167 页

梳理陌生仓库并验证搭建流程

检查仓库结构并实跑文档中的搭建步骤,记录环境缺口、测试结果,产出已验证的入门说明。

完整提示词

<context>
Setup docs are usually written once by someone whose machine already had half the tools, so they skip steps, pin old versions, or describe a flow the CI config abandoned long ago. The fastest way to find out is to follow them literally on a clean path and write down every place reality differs. The value of this run is the record, not a working checkout at any cost: a silent workaround helps one person once, while a recorded gap fixes the docs for everyone.
</context>

<task>
Explore the repository at `{{repo_path}}` and verify its setup for this goal: {{goal}}.

1. Map the repository before running anything: purpose (README), languages and frameworks (manifests), top-level layout and what each main directory holds, entry points, the test setup, external services it needs, and where configuration and secrets come from. Read README, CONTRIBUTING, AGENTS-style files, Makefiles or task runners, package scripts, devcontainer and compose files, and the CI configuration, which is often the most accurate description of a working setup.
2. Follow the documented setup for the goal literally, in order. For each step record the command, its exit status, the time it took, and the relevant output lines.
3. When a step fails or is missing, diagnose the cause (missing tool, version mismatch, undocumented environment variable, service not running, wrong order, platform difference) and try the smallest workaround that leaves tracked files unchanged: an environment variable, an untracked local config file copied from an example, a different tool version through a version manager, a step taken from CI. Record the gap and the workaround either way.
4. Run the tests the docs describe, and the app if the goal includes running it. Report real results; a failing test is a finding, not something to work around.
5. Write a getting-started note containing only commands you actually ran successfully, in order, with prerequisites and versions, to a new file outside the existing docs (for example `GETTING-STARTED.verified.md` at a path the user can review), so the maintainers can merge it into their docs.
</task>

<constraints>
- Fix nothing in tracked files: no code, config, docs or lockfile changes. Record instead.
- Do not install tools globally, use administrator rights, or change shell profiles without asking; prefer project-local or version-managed installs, and list anything installed.
- If a step needs credentials, paid accounts or access you do not have, stop that path, record it, and continue with whatever does not depend on it.
- Never skip, deselect or mark tests as expected failures to make the run look clean.
- Do not run commands that deploy, publish, send email, or touch shared or production resources, even if the docs say to.
{{> guardrails/scope-discipline}}
{{> guardrails/verify-before-done}}
{{> guardrails/no-hardcoding-to-pass-tests}}
</constraints>

<output_format>
## Map
Purpose, stack, layout (Directory | What it holds), entry points, external services, configuration sources.

## Setup log
Table: Step | Source (doc and line, or CI) | Command | Exit | Time | Notes.

## Gaps
Table: Gap | Effect | Workaround used | Suggested docs fix.

## Getting started
Where the verified note was written, and its contents.

## Verification
Test and run results for the goal, real output summarised, and anything installed along the way.
</output_format>

可替换内容

  • {{repo_path}}
  • {{goal}}
  • {{> guardrails/scope-discipline}}
  • {{> guardrails/verify-before-done}}
  • {{> guardrails/no-hardcoding-to-pass-tests}}

分类与标签

编程开发、仓库探索、环境搭建、文档验证、项目接手

前往 AI 图片创作