원클릭으로 Manus에서 모든 스킬 실행

repo-orientation

스타1

포크0

업데이트2026년 7월 12일 17:17

Use at the start of work in any BES repo to build a current, cited map of instructions, repo state, verification gates, active plans, and likely risk before editing.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

buildepicshit

buildepicshit/agentic-installation-methodology

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Repo Orientation

Use this before planning or editing.

Steps

Read the nearest AGENTS.md.
If present, read CLAUDE.md, STATUS.md, .agents/DOCUMENTATION_GUIDE.md, and the docs linked by AGENTS.md. WORKFLOW.md is the per-repo engagement contract; read its Section 1 (Universal) — it is the whole contract for every agent.
Read SESSION_JOURNAL.md at the repo root (last 3 entries). It tells you what the previous agent did, what was left dirty, and what to pick up. If absent, copy from agents/templates/SESSION_JOURNAL.template.md (or the propagated .agents/templates/SESSION_JOURNAL.template.md in a child repo).
Before dispatch, delegation, model-specific work, or multi-agent review, read agents/MODEL_ROUTING.md or the propagated .agents/MODEL_ROUTING.md.
Check git state with git status --short --branch.
Identify the active branch, tracking branch, untracked files, and unrelated local changes.
Identify the repo's verification gate and any hook setup requirements.
Locate the task's likely files with rg and rg --files.
If the area is unfamiliar, zoom out one abstraction layer: map the relevant modules, callers, data flow, and docs before choosing edit points.
Report only verified facts. Cite files or command output.

Output

Target repo and branch.
Source-of-truth docs read.
Model-routing source read when delegation or model selection is in scope.
Relevant files or directories.
One-layer-up module/caller map when the area is unfamiliar.
Verification commands.
Documentation placement constraints for this task.
Local changes that must be preserved — REAL content changes only. A stat-dirty file (mtime touched, identical to HEAD) is clean; say nothing.
Open questions — only a genuine owner DECISION that blocks the task. If none, say "none" and proceed. Do not manufacture questions to fill the slot.

Hard Rules

Do not edit during orientation.
Do not rely on memory when repo docs can answer the question.
If instructions conflict, stop and report the conflict.
A clean tree with nothing owed is the success state, not a prompt to find something to flag. Report it in one line and move to the task (agents/OPERATING_MODEL.md "Standing Autonomy and Concision").

이 저장소의 다른 Skills

같은 저장소

approved-spec-decomposition

buildepicshit/agentic-installation-methodology

BLOCKING. Use after a SPEC.md is approved and before in-execution to emit one TASK.md per executable slice into specs/<id>/tasks/. Each TASK.md carries primary/cross-validation/verification model lanes and gates the parent SPEC's transition approved -> decomposed -> in-execution. Tasks are the source-of-truth dispatchable units that agents execute directly; no external tracker (Linear) or dispatcher (Symphony) is required.

2026-07-101

code-review

buildepicshit/agentic-installation-methodology

Use for reviewing local diffs, branches, or PRs. Prioritises bugs, regressions, missing tests, unsafe assumptions, and broken repo contracts over surface polish. Do not use to author or review SPEC.md / IDEA.md artefacts — use spec-review for that BLOCKING gate.

2026-07-101

cross-agent-cli-invocation

buildepicshit/agentic-installation-methodology

Use when you (an agent) intend to invoke another agent's CLI from Bash — claude calling copilot, copilot calling claude, or any equivalent cross-agent pattern. Read at session start whenever you might fire `claude` or `copilot` from a Bash tool call. The skill documents the gotchas, points at the validator helper, and explains where the mechanical block fires.

2026-07-101

diagnosis

buildepicshit/agentic-installation-methodology

Use when debugging a failure, flaky behavior, regression, broken command, or unclear root cause. Builds a fast deterministic feedback loop before fixing.

2026-07-101

evidence-cluster

buildepicshit/agentic-installation-methodology

Use during code authoring + spec-review. Four practices bundled: (1) impact-aware test selection — run tests the changed files transitively reach, not just the ones you wrote; (2) anti-over-mock cue — no mocks outside test files; (3) complexity-delta gate during review — measure lines vs behaviour; (4) dual-reader ambiguity probe at SPEC review — second reviewer asks 'what does this permit/forbid that disagrees'.

2026-07-101

execution-discipline-cluster

buildepicshit/agentic-installation-methodology

Use during every execution-phase task AND whenever answering any question with a knowledge gap. Six practices bundled: (1) tool receipts; (2) in-flight failure disclosure; (3) receiving-code-review; (4) ground before you answer; (5) confidence-band declarations on completion-report claims; (6) escalation rubric — stop and surface or reset rather than grind. Inherits the canonical exit-code mapping from the CLI invocation contract.

2026-07-101

name	repo-orientation
description	Use at the start of work in any BES repo to build a current, cited map of instructions, repo state, verification gates, active plans, and likely risk before editing.
license	internal-only
compatibility	["copilot","claude","bes-fleet"]
allowed-tools	[]
metadata	{"bes_provenance":{"origin":"internal","source_urls":[],"borrowed_from":[],"upstream_status":"not-applicable","last_audited":"2026-06-05T00:00:00.000Z","audit_cadence":"annual","adoption_status":"bes-native","security_review":"not-required","notes":"BES fleet-native skill."},"bes_tool_surface":{"scripts":"none","network":false,"dependencies":[],"secrets":[],"allowed_tools":[],"risk_notes":"No skill-local executable helper scripts."}}

Repo Orientation

Use this before planning or editing.

Steps

Read the nearest AGENTS.md.
If present, read CLAUDE.md, STATUS.md, .agents/DOCUMENTATION_GUIDE.md, and the docs linked by AGENTS.md. WORKFLOW.md is the per-repo engagement contract; read its Section 1 (Universal) — it is the whole contract for every agent.
Read SESSION_JOURNAL.md at the repo root (last 3 entries). It tells you what the previous agent did, what was left dirty, and what to pick up. If absent, copy from agents/templates/SESSION_JOURNAL.template.md (or the propagated .agents/templates/SESSION_JOURNAL.template.md in a child repo).
Before dispatch, delegation, model-specific work, or multi-agent review, read agents/MODEL_ROUTING.md or the propagated .agents/MODEL_ROUTING.md.
Check git state with git status --short --branch.
Identify the active branch, tracking branch, untracked files, and unrelated local changes.
Identify the repo's verification gate and any hook setup requirements.
Locate the task's likely files with rg and rg --files.
If the area is unfamiliar, zoom out one abstraction layer: map the relevant modules, callers, data flow, and docs before choosing edit points.
Report only verified facts. Cite files or command output.

Output

Target repo and branch.
Source-of-truth docs read.
Model-routing source read when delegation or model selection is in scope.
Relevant files or directories.
One-layer-up module/caller map when the area is unfamiliar.
Verification commands.
Documentation placement constraints for this task.
Local changes that must be preserved — REAL content changes only. A stat-dirty file (mtime touched, identical to HEAD) is clean; say nothing.
Open questions — only a genuine owner DECISION that blocks the task. If none, say "none" and proceed. Do not manufacture questions to fill the slot.

Hard Rules

Do not edit during orientation.
Do not rely on memory when repo docs can answer the question.
If instructions conflict, stop and report the conflict.
A clean tree with nothing owed is the success state, not a prompt to find something to flag. Report it in one line and move to the task (agents/OPERATING_MODEL.md "Standing Autonomy and Concision").