agentleFS
Sign inStart free
palpenpalpen/claude-skills/orient/SKILL.md

orient

Skill0 starsChanged 7 months agoMITView on GitHub

Quick orientation check — shows which clone you're in, the current branch, dev server port, git status, and whether the dev server is running. Use when asked to "orient", "where am I", "which clone", "status", or at the start of a new session.

  • Reads credentials

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use retro, ui-ux-pro-max and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run ALL of these commands in parallel (they are independent), then format the output:

    line 22
  2. Distinctive:

    If there are uncommitted changes, list them under "Status:" instead of "clean"

    line 51
  3. Very specific:

    If the dev server is not running, show "not running" and suggest npm run dev

    line 52
  4. Distinctive:

    If PORT is not set in .env.local, show "3000 (default)" and note it's not configured

    line 53
  5. Distinctive:

    If on main, show a warning: "⚠ You're on main — create a feature branch before making changes"

    line 54
  6. Distinctive:

    If there are no commits ahead of main, say "Up to date with main"

    line 55
  7. Distinctive:

    Keep it concise — this is a quick glance, not a deep analysis.

    line 57

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Orient — Clone & Branch Status

Print a quick status dashboard for the current workspace.

Steps

Run ALL of these commands in parallel (they are independent), then format the output:

  1. basename $(pwd) and pwd — working directory and clone name
  2. git branch --show-current — current branch
  3. git status --short — uncommitted changes (empty = clean)
  4. git log main..HEAD --oneline 2>/dev/null — unpushed commits vs main
  5. grep '^PORT=' .env.local 2>/dev/null and grep '^NEXT_PUBLIC_CLONE_NAME=' .env.local 2>/dev/null — configured port and clone label (look for .env.local in the current directory and in web/ subdirectory)
  6. lsof -ti:<port> 2>/dev/null — check if the dev server is running on the configured port (use the PORT from step 5, default 3000)

Output format

Print a compact dashboard. Example:

📍 Orient
─────────────────────────────────
Clone:      job_ai_risk_evaluator--frontend-ui
Branch:     feat/frontend-ui
Port:       3001
Dev server: running ✓  (pid 12345)
Status:     clean
Ahead of main by 3 commits:
  925993f feat: add dev preview page
  aa20113 fix: remove OpenAI branding
  ccf1fce fix: simplify plan page UI
─────────────────────────────────

Adapt the output based on what you find:

  • If there are uncommitted changes, list them under "Status:" instead of "clean"
  • If the dev server is not running, show "not running" and suggest npm run dev
  • If PORT is not set in .env.local, show "3000 (default)" and note it's not configured
  • If on main, show a warning: "⚠ You're on main — create a feature branch before making changes"
  • If there are no commits ahead of main, say "Up to date with main"

Keep it concise — this is a quick glance, not a deep analysis.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free