status
Skill2 starsChanged 5 months agoApache-2.0View on GitHub
Use to inspect the current Volley lock state. Reports who's active, what task they're on, lock age, whether the named PID is still alive, and lists the most recent .volley/ review files. Use to confirm Codex finished, to check for stale locks, or any time you're unsure whose turn it is.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- SuresoftTechnologies/statica-plugintheir own version, first seen Nov 15, 2026
- librosdeia/builder-method-claude-plugintheir own version, first seen Nov 15, 2026
- rmyndharis/mandortheir own version, first seen Nov 15, 2026
- XORwell/archeflowtheir own version, first seen Nov 15, 2026
- cpoder/claude-apple-plugintheir own version, first seen Nov 15, 2026
- AgentLTL/agentltl-claude-codetheir own version, first seen Nov 15, 2026
Used with
Projects with it also use off, list and 10 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.
StakeholderSenseiSkilloff
Disable polygraph for this repo (user-only escape hatch; all hooks no-op)
Also in 4 projects that use this
SuShuhengSkilllist
Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.
Also in 8 projects that use this
kennethleungtySkillpause
Pause — stop the music (alias for /stop)
Also in 6 projects that use this
codebycoreySkillnew
Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.
Also in 7 projects that use this
michaelenglandSkillimport
This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.
Also in 5 projects that use this
genomewalkerSkillresume
Resume a thread by loading its ~800-token context capsule
Also in 15 projects that use this
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- anthropics/claude-for-legal★ 9.5ksame name
- microsoft/TokenEconomizer★ 6.2ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- H-mmer/pentest-agents★ 815same name
- emotixco/claude-skills-founder★ 796same name
- me2resh/apexyard★ 542same name
- dsifry/metaswarm★ 432same name
- ffroliva/gflow-cli★ 367same name
- serithemage/serverless-openclaw★ 196same name
177 more not listed
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.
In this repository7 other files it gives its agents.
- diagnoseSkill
- implementSkill
- review-codeSkill
- review-planSkill
- review-prSkill
- setupSkill
- unlockSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read-only inspection of the Volley state.
- Very specific: line 12
Verify
.volley/exists: If not, tell user to run /volley:setup first and stop. - Very specific: line 33
List recent
.volley/artifacts: If no artifacts exist yet, show (no review artifacts yet) instead of a blank section. - Very specific: line 74
If ACTIVE=codex and alive: volley_next_step_done "Codex is currently working.
- Very specific: line 75
If ACTIVE=claude and TASK=done: volley_next_step "/volley:review-code" "Codex finished.
“Common” is measured: kept by at least 6 in 10 of the 154 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
/volley:status
Read-only inspection of the Volley state. Never modifies anything.
Steps for Claude
- Verify
.volley/exists. If not, tell user to run/volley:setupfirst and stop. - Read STATE. Source the lib and read all four keys. If any key read fails (missing file, missing key, or malformed STATE), report the error to the user verbatim and stop - do NOT continue with empty/default values.
. "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh" ACTIVE=$(volley_state_get .volley/STATE ACTIVE) || exit 1 TASK=$(volley_state_get .volley/STATE TASK) || exit 1 SINCE=$(volley_state_get .volley/STATE SINCE) || exit 1 PID=$(volley_state_get .volley/STATE PID) || exit 1 AGE=$(volley_state_lock_age .volley/STATE) || exit 1 - Check PID liveness if ACTIVE=codex.
if [ "$ACTIVE" = "codex" ] && [ "$PID" != "0" ]; then if volley_state_pid_alive "$PID"; then PID_STATUS="alive"; else PID_STATUS="DEAD"; fi else PID_STATUS="n/a" fi - List recent
.volley/artifacts. If no artifacts exist yet, show(no review artifacts yet)instead of a blank section.ARTIFACTS=$(ls -lt .volley/*.md 2>/dev/null | head -5) [ -z "$ARTIFACTS" ] && ARTIFACTS="(no review artifacts yet)" - Read continuity config for the report (non-mutating). If
.volley/config.jsonexists, parse it (host JSON, no jq) and resolve the review/implementationmodel+reasoningEffort(inherit→ show "Codex default"). If.volley/local.jsonexists, note whether repo identity matches (volley_repo_identity_matches) and which roles have a stored thread/session id (presence only - never print the id or any secret). Absent files → report "defaults / not initialized". - Report to user. Format like this:
Volley Status ────────── Active actor: <ACTIVE> Current task: <TASK> Lock since: <SINCE> (<AGE>s ago) Recorded PID: <PID> (<PID_STATUS>) Continuity ────────── Review model: <model / Codex default> (effort: <effort>) Impl model: <model / Codex default> (effort: <effort>) Repo identity: <match | mismatch → will rehydrate | not initialized> Saved threads: planReview=<yes/no> prReview=<yes/no> implementation=<yes/no> Local state: .volley/local.json Checkpoint: <managedCheckpoint path> Recent artifacts: <ls output> Detect stale lock. Stale =
ACTIVE=codexAND one of:PID != 0AND PID is dead, ORAGE > 1800seconds (30 minutes).
PID=0is the documented "untracked" sentinel (set by/volley:implementbecause the spawnedwtPID is useless for liveness). WhenPID=0, fall back to age-only detection. If stale, print:⚠ STALE LOCK detected. Codex's session looks abandoned (no progress for >30 min, or process ended). Run /volley:unlock to clear it.- Print the next-step block. Decide based on state:
- If stale:
volley_next_step "/volley:unlock" "Clear the stale lock so Claude can resume." - If
ACTIVE=codexand alive:volley_next_step_done "Codex is currently working. Watch the terminal tab; re-run /volley:status when it finishes." - If
ACTIVE=claudeandTASK=done:volley_next_step "/volley:review-code" "Codex finished. Review the diff against the plan." - If
ACTIVE=claudeandTASK=idle:volley_next_step "/volley:review-plan" "Ready for the next handoff. If you have a plan to review, send it to Codex." - Otherwise (Claude active mid-task):
volley_next_step_done "Claude is mid-task. Continue working in this session."
- If stale:
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.

