orient

Audit git repository state and manage GitHub issue task claims.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/evanharmon1/harmon-devkit --skill orient-evanharmon1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orient
Source: https://github.com/evanharmon1/harmon-devkit/tree/main/ai/skills/universal/orient
Command: npx skills add https://github.com/evanharmon1/harmon-devkit --skill orient-evanharmon1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, task.

What problem does it solve?

This skill solves the problem of fragmented development sessions by providing a consistent, automated ritual to assess repository state and maintain clear, searchable session history.

Core Features & Use Cases

  • Context Awareness: Automatically aggregates git status, branch information, and active GitHub issues or PRs to provide a snapshot of the current workspace.
  • Stale Claim Cleanup: Identifies and reports abandoned tasks or stale issue assignments that persist after a session has ended.
  • Session Management: Standardizes session naming conventions to ensure work is easily identifiable in mobile and desktop session pickers.

Quick Start

Invoke the orient skill by typing /orient followed by the current topic or issue number to generate your session name and status report.

Frequently Asked Questions about orient

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize development session starts and track git workflow progress?

To standardize development session starts, you can audit your repository state and manage task claims across git branches and GitHub issues. This provides a consistent, automated snapshot of your current workspace and maintains clear, searchable session history.

What is the best way to clean up stale GitHub issue assignments after a session ends?

Cleaning up stale GitHub issue assignments involves auditing your active branches and issue trackers to identify abandoned tasks. The skill automatically detects and reports these stale task claims that persist after a session has ended, keeping your workflow clear.

How do I check git status and active GitHub issues before starting a coding session?

Checking git status and active GitHub issues before coding requires aggregating repository state data automatically. By running the orient command with your current topic or issue number, you generate a comprehensive status report and standardized session name.

Do I need the GitHub CLI to automate repository state checks and session management?

Yes, you need the GitHub CLI and git installed to automate repository state checks. The session management process requires integration with both git and the GitHub CLI to perform status checks, audit branches, and manage active issue assignments.

Can I standardize session naming conventions for mobile and desktop session pickers?

You can standardize session naming conventions to ensure your work is easily identifiable across mobile and desktop session pickers. By invoking the orient skill with a topic or issue number, it generates a standardized, searchable session name automatically.

Why does my development workflow have fragmented sessions and stale task claims?

Fragmented development sessions and stale task claims occur when repository state is not audited consistently before starting work. Without an automated initialization ritual to check git branches and GitHub issues, abandoned assignments persist and session history becomes disorganized.