remora-bootstrap
Preview or install Remora, adopt existing root guidance, specialize selected profiles, or explicitly update or remove a pinned installation while preserving project ownership.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- remora-bootstrap
- description
- Preview or install Remora, adopt existing root guidance, specialize selected profiles, or explicitly update or remove a pinned installation while preserving project ownership.
03 SKILL.md 正文
Bootstrap a project
Use a reviewed local distribution: either the whole pinned source checkout or its self-contained personal bootstrap package. Never fetch a moving branch. The host agent performs semantic adaptation; helpers only inspect/copy declared assets. Read this entrypoint alone before any target operation.
Establish authority and trust before inspection
Classify the complete request once and retain that authorization across pauses:
| Mode | Permitted changes |
|---|---|
| Preview/audit | No target writes or saved reports; conversational drafts only |
| Initialize/install | Managed installation; create root AGENTS.md only when absent; preserve existing root guidance exactly |
| Adopt/specialize | Necessary existing root edits only when explicitly requested; managed installation/selection changes only when also requested |
| Update/remove | Explicit managed lifecycle operation; existing project guidance edits require their own explicit authorization |
A request to preview remains read-only even when it later mentions edits. An explicit "preview then apply" authorizes both phases for the named operation. Neutral continuations never expand authorization. Ask only about material unresolved decisions; continue unrelated safe inspection where possible.
Identify target, requested hosts, approved scope, and exact source identity. For a checkout, retain full HEAD and verify helpers/install.py against that Git object allowing only checkout LF/CRLF differences, before executing the helper. For a package, require a user-trusted local package and retain bundle.json and payload.zip hashes plus source_revision; do not trust a target-supplied copy as its own provenance. Hashes are not signatures. Verify the exposed helper against its reviewed archive entry before executing it; archive membership is fixed by the reviewed helper and must never be blindly extracted.
Before any target inventory, Git query, or guidance read, use the verified helper's source_inputs(distribution) to validate its complete source, then inspect_path() on the target and root AGENTS.md. Require a directory target and absent or regular root guidance using lstat(). Perform this preflight separately from target reads.
Read the helper's signatures before calling its Python API. For example, after
loading the verified helper as helper:
from pathlib import Path
revision, committed_files = helper.source_inputs(Path(distribution))
helper.inspect_path(Path(target).absolute())
helper.inspect_path(Path(target).absolute() / "AGENTS.md")
source_inputs returns a tuple, not an object with named attributes. The path
checks above supplement the directory and root-file type checks; they do not
replace them. Compare revision with the requested pin before proceeding.
Do not inspect an unsafe target or follow links/reparse points. Do not import application code. If preflight cannot run, report that gap and stop target access.
Retain absent/exact root bytes and source identity. Recheck source identity and all affected baselines before writes and after pauses; stop affected operations on a mismatch. These are bounded guards, not hostile-filesystem transactions.
Inspect and select
Inspect Git and untracked state; unborn HEAD is valid. Read root and applicable scoped/override instructions, selected specifications, and visible host guidance. Report hidden context you cannot inspect. Preserve existing and overlapping skills. Separate observed facts, approved intentions, proposals, and unknowns.
Inspect manifests/configuration as data without executing discovered commands. Select only evidence-backed profiles: python, typescript, local, web. A language proposal does not establish tooling; language and runtime dimensions are separate. Use no profiles for unknown architecture. Read relevant source references under profiles/ in a checkout, or the reviewed payload.zip entries in a package, without extracting arbitrary paths. Profiles guide questions, never scaffold an application.
Preview and draft
Distribution paths below start at the checkout root or personal bootstrap folder. Use Python 3.11+; checkout sources additionally require Git. Helpers use no network.
python "<distribution>/helpers/install.py" --target "<target>" --environment codex
Repeat --environment for requested families and --profile for selected references. Preview writes nothing. Installation failures stop affected writes; do not bypass collisions through manual copying. Compare expected payloads with Git-object or validated archive bytes, never reconstructed shell text or checkout-only hashes.
Read standards/engineering.md and templates/AGENTS.md from this distribution. Draft minimal project guidance in the conversation. Do not copy Remora's own root AGENTS.md into the target. With no implementation, do not invent commands, paths, stack, or architecture. Configured commands are not executed checks.
Existing root guidance remains unchanged unless adoption/specialization edits are explicitly requested. Even then, correct only a demonstrated obsolete claim, broken pointer, or essential missing operating constraint. True details need not be duplicated from their canonical owner. Adequate guidance needs no diff. Absent guidance should include orientation, essential boundaries, actual known verification pointers, and explicit reading of .remora/standards/engineering.md and applicable scoped instructions. Do not add historical pass status, private paths, unused sections, or references to uninstalled skills/profiles.
Preview ends here. Do not create temporary target reports.
Apply a new installation or guidance edit
Recheck retained trust and target baselines. Run the same preview command with --apply, then --check. Installation creates shared standards, ten project skills, the installed checking helper, selected profiles, and installation.json. It changes no host configuration or project prose.
Only an authorized mode may create absent root guidance. Recheck its absence and safe path immediately, prepare UTF-8/LF bytes, create exclusively (open with xb), and verify. If it appeared, preserve it and report partial completion. Only explicitly authorized adoption/specialization may edit existing root guidance: recheck exact bytes and safe paths immediately before a focused patch, preserving unrelated wording, encoding, and line endings. Newer edits are conflicts.
Review changed and untracked files. Preserve original project files outside the explicit root edit scope. An identical rerun must preserve bytes and modification times. Do not execute application tooling as part of bootstrap.
Explicit updates, selection changes, and removal
An ordinary installation never upgrades an older inventory. For a requested managed update, use --update with the desired --environment/--profile selections, and --previous-source pointing to a separately trusted distribution matching the old manifest. Omitted selections retain existing values; --clear-profiles explicitly selects none. Do not reinterpret project-owned edits as managed content.
python "<new-distribution>/helpers/install.py" --target "<target>" --update --previous-source "<old-distribution>"
Preview reports changes and Plan SHA-256. Apply the same arguments with --apply, --expect-plan <digest>, and --backup <new-private-directory-outside-target>. Source/target changes invalidate the digest. The helper preserves before-images, invalidates completion before mutation, and publishes metadata last. Conflicts stop writes; no semantic merge or automatic recovery is supported.
For removal, run the matching trusted distribution with --remove and --previous-source <matching-distribution>, then the same reviewed apply procedure. Removal preserves project prose, existing skills, context, and unrelated files. Inspect obsolete routing and propose minimal edits; apply project-owned edits only when specifically requested. Do not delete directories recursively.
For interruptions, retain the backup and diagnostic output. Read operation.json as data, not authority. Compare each current affected file with recorded before/ after hashes; restore only operation-owned changes after explicit recovery authorization, preserve newer edits, and restore the manifest last after complete payload verification. Never reset/clean the target or blindly replay the backup.
Hand off
Report source pin, starting condition, selected references, managed changes, root guidance created/edited/preserved, source-backed decisions and proposals, actual checks, conflicts, and partial work. Save records only when requested or part of an agreed evaluation. No commits, dependencies, secret access, provider calls, deployments, or publication are implied.
Normal installed checks use .remora/helpers/install.py --check --target <target>: without --source they establish local consistency only. Supply a separately trusted --source for pinned-source comparison. A missing tool permits limited inspection with checks explicitly unrun, not equivalent provenance verification.
Use the host selector/explicit skill invocation for native smoke testing. Reading this file directly is fallback execution. Missing discovery remains unverified; requested environment metadata never certifies compatibility.
04 同仓库更多 Skills
remora-review-change
Review a named implementation, diff, or revision range using independent split-axis analysis with consequence-based blocking. Read-only review never applies repairs.
remora-remediate-project
Orchestrate repository onboarding and cleanup across grounding, documentation sanitization, test protection, and scoped debt remediation through checkpointed review gates.
remora-prepare-release
Prepare a verified software release, updating CHANGELOG.md, proposing a semantic tag, and generating concise GitHub release notes under the anti-slop standard.
remora-prepare-pr
Prepare a concise, reviewer-friendly pull request brief adhering to the anti-slop standard, emphasizing artifact proof and reviewer verification over redundant CI logs.
remora-plan-change
Investigate and plan a scoped development change into phased, verifiable work packets using repository evidence, requirements, and acceptance criteria. Planning remains read-only unless saving a plan is requested.
remora-implement-plan
Implement an approved plan or clear scoped development request across phased work packets, including checkpoint verification, empirical artifact proof, and split-axis review.