session-manager-dev

Plugin session-manager-dev from marketplace session-manager in StanislavBG/claude-code-session-manager. Commands read from the repo's manifest — 4 days ago.

Skills (10)

• builder:diff

  Step 0 of builder — determine everything on HEAD that hasn't been published yet. Prefer the project's actual npm registry state over git tags, since a tag can exist without a matching publish (or vice versa); fall back to the last git tag when there's no resolvable package name or no network.

• builder:classify-and-bump

  Step 1 of builder — parse conventional-commit prefixes from the commit list produced by builder:diff and decide the semver bump. Never guess when the history doesn't follow the convention — ask the user instead.

• builder:gate

  Step 2 of builder — run typecheck and unit tests, both time-bounded, as the hard pre-publish gate. A failing gate stops the pipeline; builder:publish never runs on a red gate.

• builder:publish

  Step 3 of builder — the ISOLATED WORKTREE publish technique. Bumps the version, tags, then does the actual build+publish from a clean git worktree checked out at that tag so the live/dirty working directory is never touched by prepublishOnly's build step. Every command below was run for real 4 times

• builder:manual

  Keep The Session Manager Field Manual — the free guide published at bilko.run/manual — in step with what actually shipped. Runs after builder:publish (or standalone), diffs the just-released commits against the manual's chapter map, revises the affected chapters, bumps the manual's own version, buil

• builder:report

  Step 4 of builder — summarize the completed (or stopped) publish run in one report — version bumped, commits covered, npm dist-tag verified, git push confirmed.

• builder

  Watch the current project's git history against its published npm package and drive the next publish — diff HEAD against the last release, classify + bump the version from conventional-commit prefixes, gate on typecheck/tests, publish from an isolated git worktree (never the live working directory),

• develop

  Lead a software-development task: analyze it from five angles, split it into small self-contained PRDs (an independent set, or a 3-5 PRD chain), queue them for the session-manager scheduler with the required gate and files, each pointing the headless executor at the engineering standards file, then

• maintaining-md-network

  Reviews, audits or drift-checks a project's CLAUDE.md and wider markdown network (CLAUDE.md, AGENTS.md, rules, skills, docs, READMEs, auto memory) so agents start from one short entry map and find each fact in exactly one place, with nothing stale. Use when the user asks to review, audit, clean up,

• send-feedback

  Hand a finding from THIS project to a DIFFERENT project on this machine, by opening a proposed feedback session in that project's own Sessions queue via Session Manager's cross-project conduit (the feedback_open_session MCP tool). Use whenever work in one repo surfaces something that is genuinely an

Similar plugins