claude

whose-turn

Whose Turn, the Claude Code side of a local monitor of your Jira, GitHub, Linear and other sources: whose turn it is, what changed, your own to-dos, a summary at the start of each session, a hand-off from the monitor window into the session, a /whose-turn command that opens the window, and an MCP server for any agent. The monitor itself is the published whose-turn npm package; the plugin installs its latest version into the monitor's data directory on first start and runs it from there; each newer version is then announced in its window and at session start and installs only when the user says yes or clicks Update. Employer-specific values live in a workspace config on the machine, not in the plugin.

2 on GitHubby Roman Maslennikovv1.0.21MITupdated 3 days agoengineering
/

Plugin whose-turn from marketplace bladeforge in aquivalabs/BladeForge. Commands read from the repo's manifest — 2 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (1)

  • whose-turn

    Use when the user asks what is going on with their tasks, what is waiting on them, what changed, or whose turn it is, in any language; asks to add, finish or list a personal to-do or something not to forget; wants to connect a source or set up the monitor, open its window, or file a bug or an idea a

Slash commands (1)

  • /whose-turn:whose-turn

    Open the Whose Turn monitor window

MCP servers (1)

  • whose-turn

    runs: node ${CLAUDE_PLUGIN_ROOT}/bin/mcp.mjs

Hooks (2)

  • SessionStart

    node "${CLAUDE_PLUGIN_ROOT}/bin/summary.mjs" hook

  • UserPromptSubmit

    node "${CLAUDE_PLUGIN_ROOT}/bin/inbox-hook.mjs"

View source on GitHub

More from aquivalabs/BladeForge

All 25 plugins →

review

claude

Stack-agnostic pre-push review framework — eight reviewer agents (five on by default, plus skill, leak and security-scan for repos that publish skills), the /review orchestrator, and the secret-scan + attestation gate, all driven by a per-project .claude/review.config.json.

2 skills · 2 commands · 8 agents

2

meta

claude

Meta skills — authoring new skills, the OCKHAM minimal-entities discipline, and the WITTGENSTEIN clarity gate for specs & plans.

10 skills

2

Frontend Vue 3 skills — single-file components with Composition API and TypeScript, component architecture, BEM in scoped styles, Pinia stores, VueUse-first composables, Nuxt conventions, motion, testing.

9 skills

2

Frontend React skills — component structure, hooks registry, skeleton components, Storybook stories.

8 skills

2

Personal Salesforce skills — Apex test authoring standard and salesforce-dx MCP usage.

5 skills

2

cerberus

claude

CERBERUS — the two-headed guard at the gate for a PUBLIC skills marketplace. A PostToolUse hook fires on every skill / reference / script / eval / manifest edit and reminds you to run BOTH heads before committing: cerberus:leak-check (outward — no real work identifier or secret escapes into the public marketplace) and cerberus:security-scan (inward — the eight-point consumer-safety checklist: prompt injection, exfiltration, secrets, dangerous commands, obfuscation, external fetches, credential access, privilege escalation, so nothing unsafe reaches whoever installs the skill). Before a push it also guards the commits themselves — their messages, authors and branch name, which no file check reads: a classic PreToolUse hook has a nested claude judge the outgoing commits and blocks a push that leaks or that it cannot judge, and on Claude Code 2.1.292 or newer a push-guard mod judges them in-process first; an older Claude Code gets a red notice at session start to update. The verdict cache is guarded best-effort, so the hook stops a forgotten check, not a deliberate forgery. Both are agent judgment passes, no denylist by design — a list of the real names to catch would itself be the leak; the intelligence lives in the agent, not a regex.

2 skills · hooks

2

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

Metrics collection, logging infrastructure, distributed tracing, SLO implementation, and monitoring dashboards

4 skills · 2 commands · 4 agents

wshobson/agents 42,461

Long-term semantic memory for Claude Code, powered by OpenViking

5 skills · 1 command · 1 MCP server · hooks

volcengine/OpenViking 42,126

Repomix MCP server for AI-powered codebase analysis. Pack local/remote repositories and search or read the generated outputs. Foundation plugin that enables all Repomix features in Claude Code.

1 MCP server

yamadashy/repomix 29,255

Real-time statusline showing context usage, active tools, running agents, and todo progress. Always visible below your input, zero config required.

1 skill

jarrodwatts/claude-hud 29,182

Architecture diagrams, explanations and Mermaid source for any public GitHub repository, from gitdiagram.com.

2 skills · 1 MCP server

ahmedkhaleel2004/gitdiagram 18,884

Maintain whose-turn?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins25 plugins