← ClaudeAtlas

orientlisted

Orient in the current project. On first contact with an unprepared project, set up the workflow's operating requirements, then orient. Run autonomously. Use for /orient requests.
amurshak/hephaestus · ★ 2 · AI & Automation · score 68
Install: claude install-skill amurshak/hephaestus
<!-- requires: none --> <!-- chains: /worktrees --> <!-- generated from .ai/workflows/orient.md; do not edit directly --> > **Codex:** this skill is the `/orient` adapter. For chained workflows (/worktrees), invoke the matching generated skill (for example `heph:<workflow>`) when it is available; otherwise read and follow `.agents/skills/<workflow>/SKILL.md`. Use Codex role agents from `.codex/agents/` when the runtime exposes them; otherwise perform the work directly and keep the same structured output. Orient in the current project. On first contact with an unprepared project, set up the workflow's operating requirements, then orient. Run autonomously. > Each project should own its orient command — `install.sh` scaffolds one from `templates/orient.md` and never symlinks this file. This shipped version is the generic fallback (plugin and manual-copy installs): it bootstraps missing setup, then orients. ## Step 1 — Detect repo `git remote get-url origin` — derive `<owner>/<repo>` for all `gh` commands. If there is no remote, work local-only and skip issue listing. ## Step 2 — Setup check Hephaestus is an adjunct to the host codebase. Verify its operating requirements and bootstrap what's missing — all writes are additive; never overwrite or modify existing content beyond appending a missing section. Skip items 1–2 when the repo *defines* these requirements rather than consuming them — the workflow source itself, recognised by `.ai/workflows/` alongside a `scripts/sync