Orient
- 646 installs
- 1 repo stars
- Updated May 26, 2026
- camacho/ai-skills
orient is a Claude skill that fetches GitHub issue context, auto-detects task type, maps a branch prefix, and generates a concise context brief for developers starting work on a tracked issue.
About
orient is a camacho/ai-skills phase-gate skill that must complete before the Isolate checkpoint in an EXPLORE workflow. Step one runs gh issue view with JSON fields for title, body, labels, and assignees when an issue number is provided; without gh or GH_TOKEN, the skill falls back to manual task description. Step two auto-detects task type from labels or keywords and maps each type to a branch prefix via a built-in lookup table. Developers reach for orient when starting GitHub-tracked work and needing a structured brief with correct branch naming before writing code.
- Fetches GitHub issue context using the gh CLI
- Auto-detects task type and maps to conventional branch prefix (fix/, feat/, chore/, docs/)
- Scans and surfaces relevant ADRs with conflict detection
- Checks for interrupted work via .branch-context.md
- Delivers a compact orientation brief before the Isolate phase
Orient by the numbers
- 646 all-time installs (skills.sh)
- Ranked #641 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/camacho/ai-skills --skill orientAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 646 |
|---|---|
| repo stars | ★ 1 |
| Security audit | 2 / 3 scanners passed |
| Last updated | May 26, 2026 |
| Repository | camacho/ai-skills ↗ |
How do you brief a GitHub issue before coding?
Quickly understand a GitHub issue, detect its type, surface relevant architecture decisions, and generate a concise context brief before starting work.
Who is it for?
Developers using gh CLI who start feature work from numbered GitHub issues and need typed branch prefixes plus a context brief.
Skip if: Repositories without GitHub Issues or workflows that begin from ad-hoc tasks with no issue tracking or gh CLI access.
When should I use this skill?
The user provides a GitHub issue number or describes a new task and needs EXPLORE orientation before implementation.
What you get
Context brief with issue metadata, detected task type, and recommended branch prefix before Isolate phase.
- Issue context brief
- Detected task type
- Branch prefix recommendation
Files
Phase gate: EXPLORE checkpoint. This skill MUST complete all steps before proceeding to Isolate.
Steps
1. Fetch issue context (if issue number provided):
gh issue view <number> --json title,body,labels,assigneesIf no issue number provided, ask the user to describe the task. If gh is not available (remote session without GH_TOKEN), skip issue fetch and proceed with manual description.
2. Auto-detect task type from labels or description:
| Label / keyword | Type | Branch prefix |
|---|---|---|
bug, error, crash, broken, fix | Bugfix | fix/ |
enhancement, feature, add, want, should, new | Feature | feat/ |
chore, config, deps, ci, tooling | Chore | chore/ |
docs, documentation, readme | Docs | docs/ |
| Default | Feature | feat/ |
3. Scan for relevant ADRs:
ls "$(git rev-parse --show-toplevel)/ai-workspace/decisions/"*.md 2>/dev/null | head -20Check ADR titles/filenames for keywords matching the issue title/body. If matches found, read the relevant ADR and surface it. If ADR scan finds contradictions, surface explicitly: "This task may conflict with ADR-NNN"
4. Check for interrupted work: If "$(git rev-parse --show-toplevel)/.branch-context.md" exists, read it and include in the brief (resuming work).
5. Read recent memory:
tail -20 "$(git rev-parse --show-toplevel)/ai-workspace/MEMORY.md" 2>/dev/null6. Present brief:
## Orient Brief
**Task**: [title or description]
**Type**: [bugfix/feature/chore/docs] → branch prefix: [fix/feat/chore/docs]/
**Suggested branch**: [prefix]/[kebab-case-name]
**Relevant ADRs**: [list or "none found"]
**Resuming?**: [yes — from .branch-context.md / no]
**Files likely affected**: [educated guess from issue description + ADR context]7. Auto-route using the one-sentence rule:
- Can the entire diff for this task be described in ONE sentence? → Direct to Isolate (skip Design/Review)
- Otherwise → Plan first (proceed to Design after Isolate)
Present the routing decision. The agent auto-decides — no human input required. If human is present, they can override.
Edge Cases
- No issue number + no user description → ask for a description
ghnot available → skip issue fetch, proceed with manual description- No ADRs directory → skip ADR scan
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What GitHub command does orient use?
orient runs gh issue view with --json title,body,labels,assignees when given an issue number. If gh is unavailable or GH_TOKEN is missing in a remote session, orient skips the fetch and uses a manual task description.
Where does orient fit in the workflow?
orient is the EXPLORE checkpoint phase gate in camacho/ai-skills. The skill must finish issue fetch, task-type detection, and brief generation before the workflow proceeds to the Isolate phase.
Is Orient safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.