claudecodex

development-flow

Feature planning, plan-to-issues, parallel-lens code review, native Claude goal pause, PR babysitting, batch-approved PR Butler with shared local history, and tailnet sharing.

1 on GitHubby Emil Fleronv3.3.0MITupdated 12 days ago
/

Plugin development-flow from marketplace my-plugins in Fleron/Claude-plugins. Commands read from the repo's manifest — 11 days ago.

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

What it installs

Skills (7)

  • babysit-pr

    Use when the user asks to monitor, watch or babysit a pull request, keep an eye on CI, handle incoming review comments, or stay on top of failures and feedback on an open PR until it is merged or closed.

  • code-review

    Use when the user asks for a review of the current diff, branch or pull request, wants a final check before shipping or opening a PR, asks what is wrong with what was just built, or says code-review.

  • feature-planning

    Use when the user wants to be interviewed about an idea, asks to grill them, wants a detailed spec, plan or issue written before any code, or says feature-planning. Also use before starting any feature or non-trivial change that has no plan yet.

  • goal-control

    Pause native Claude goal continuation when the user explicitly asks to stop or pause, or when work cannot continue without an external decision or unavailable prerequisite. Claude only.

  • plan-to-issues

    Use when the user points at a GitHub issue or milestone that holds a plan or spec and asks to break it down, split it into tasks, make it delegable, create sub-issues, or says plan-to-issues.

  • pr-butler

    Use when the user wants to catch up on their authored PRs in a repository, see what needs attention and what changed since last time, or prepare several PRs through an approved batch of repairs. Keeps shared local history for Claude and Codex. A one-shot session, not continuous PR monitoring.

  • tailnet-share

    Use when the user asks to share, publish or send a link to a local HTML file, report or presentation, wants a URL for something built in the session, mentions tailnet or Tailscale Serve, or asks to set up sharing on a new machine.

Subagents (2)

  • code-reviewer

    Read-only reviewer that applies one code-review lens to a diff. Dispatched by the code-review skill once per lens, with the lens file path and the scope in the prompt.

  • plan-reviewer

    Reviews a feature-planning plan before it reaches the human. Invoked by feature-planning.

Hooks (2)

  • SessionStart

    if [ -n "${CLAUDE_ENV_FILE:-}" ] && [ -n "${CLAUDE_PLUGIN_ROOT:-}" ]; then node "${CLAUDE_PLUGIN_ROOT}/scripts/goal-control.mjs" session-start; fi

  • Stop

    if [ -n "${CLAUDE_PLUGIN_DATA:-}" ] && [ -n "${CLAUDE_PLUGIN_ROOT:-}" ]; then node "${CLAUDE_PLUGIN_ROOT}/scripts/goal-control.mjs" stop; fi

View source on GitHub

More from Fleron/Claude-plugins

All 11 plugins →

A full scaffolding and claude harness for e2e development

8 skills · 6 agents

1

Adds a thorough and complete end 2 end workflow for feature development.

4 skills · 6 agents · hooks

1

autopilot

claude

A full scaffolding and claude harness for automated development together with claude-control.

4 skills

1

Adds a minimal /goal wrapper around the installed ccctl goals CLI.

1 skill · 1 command

1

Adds a /commit and /commit-push-pr skill for quick code commits with conventional commit messages.

2 commands

1

ponytail

claudecodex

Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.

2 skills

1

Maintain development-flow?

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 plugins11 plugins