where
Skill1 starsChanged 50 days agoMITView on GitHub
Branch, phase, NEXT, PRs, what waits on you. Use for "where am I", "what's next".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- agoopintsai/shiprighttheir own version, first seen Nov 1, 2026
- ARCASSystems/FounderOStheir own version, first seen Oct 24, 2026
- Emin4ik/StateNesttheir own version, first seen Oct 20, 2026
- bingelp/skillstheir own version, first seen Oct 20, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ARCASSystems/FounderOS★ 7same name
- agoopintsai/shipright★ 2same name
- bingelp/skills★ 0same name
- Emin4ik/StateNest★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Run this with the Bash tool, exactly as written:
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
Run this with the Bash tool, exactly as written:
PY "${CLAUDE_SKILL_DIR}/../../scripts/where.py"
PY is python on Windows and python3 elsewhere; use py -3 only if both fail.
Show the output verbatim in a code block.
After it, add at most one sentence, and only when the output shows something to act on: red checks, a PR to retarget, a phase branch that differs from the current branch, a stale NEXT, or items waiting on the user. For a step the user must take, give the command that does it, ready to paste in a terminal, as the PR line shows it (gh pr merge 13 --merge). Do not read docs or run other commands to embellish it.
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
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.