pipeline

Plugin pipeline from marketplace claudeframework in dixus/claudeframework. Commands read from the repo's manifest — 6 days ago.

Skills (24)

• 0_spec

  Write a feature spec from requirements in .claude/input/. Use when starting a new feature, before implementation begins.

• 1_implement

  Implement a feature from a spec file in .claude/specs/. Use after a spec is written and approved.

• 2_review

  Review implementation changes and write a report to .claude/reviews/. Use after implementation is complete, before merging or committing.

• 3_fix

  Fix issues found in a review report in .claude/reviews/. Use after a review identifies issues that need fixing.

• apply-proposals

  Review and apply accepted proposals from learn-proposals.md to skill and rule files. Closes the scout→learn→apply loop. Use after reviewing proposals and marking them as accepted.

• audit

  Audit dependencies for vulnerabilities and scan for committed secrets. Use periodically or when security alerts flag a dependency.

• changelog

  Write or refresh the per-ticket changelog file (changelog/<branch>.md) for the current ticket branch. Use before committing or pushing work on a ticket branch when NOT running the full /pipeline:ship pipeline — the changelog is what feeds the work item's manual-steps flag and the release notes.

• commit

  Create well-structured atomic commits with conventional commit messages. Use when ready to commit working changes.

• continue

  Resume work from a handoff file. Use at the start of a new session to pick up where a previous session left off.

• create-hook

  Scaffold a Claude Code hook (command or HTTP) for this project. Use when you want to automate quality checks, formatting, or notifications on tool events.

• debug

  Diagnose and fix a failing test, type error, or runtime error. Use when a specific test or build step is failing.

• decompose

  Break a concept document, draft, or product brief into independent PRDs that each feed into /pipeline:ship. Use when input contains multiple features or a big-picture vision.

• doc

  Regenerate .claude/docs/ from current skills and context. Use after adding or modifying skills, context files, or framework structure.

• fleet

  Ship decomposed PRDs in parallel. Analyzes file conflicts, groups into batches, runs /pipeline:ship in isolated worktrees, merges results. Use after /pipeline:decompose.

• handoff

  Capture current session state to a handoff file. Use before /clear, when context is getting full, or when ending a session mid-task.

• harvest

  Clone and analyze a Git repo's Claude Code setup. Discovers adoptable skills, hooks, agents, and patterns, then generates adoption proposals. Use after /pipeline:scout finds interesting repos, or directly with a repo URL.

• healthcheck

  Scan Docker container logs for errors, crashes, and warnings. Use when services are misbehaving or after a deployment to verify health.

• impact

  Analyze blast radius of a code change — find all call sites, test mocks, and consumers. Use before modifying shared functions, interfaces, or modules.

• learn

  Process references into skill/rule improvement proposals. Use after adding blog posts, repos, or docs to .claude/references/, or pass a URL to fetch and ingest directly.

• release-notes

  Aggregate per-ticket changelogs into a quarterly release-notes file (releases/<quarter>.md), surfacing the manual deployment steps an operator must perform on top of the automatic release pipeline.

• release

  Cut a quarterly release. Branches `Q<N>-Release-<YYYY>` from the main branch, generates release notes via `/pipeline:release-notes`, tags the cut, and pushes — with a gate before any push.

• scout

  Search the web for new Claude Code patterns, release notes, and community skills. Use periodically to check for framework optimization opportunities.

• ship

  Orchestrate the full spec → implement → review → fix → commit pipeline. Use when shipping a complete feature end-to-end.

• smoke

  Write and run smoke tests against the Docker stack from a spec. Use after deploying to a Docker environment to verify end-to-end behavior.

Slash commands (2)

• /pipeline:rebase-master

  Fetch origin/master and rebase the current branch onto it

• /pipeline:review

  Review the current branch diff for issues before merging

Subagents (2)

• code-reviewer

  Expert code reviewer. Use PROACTIVELY when reviewing PRs, checking for bugs, or validating implementations before merging.

• explorer

  Codebase exploration specialist. Use when investigating how a feature works, tracing data flow, or understanding architecture before making changes.

Hooks (4)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/inject-instincts.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/protect-secrets.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/auto-format.js"

• PostCompact

  node "${CLAUDE_PLUGIN_ROOT}/hooks/post-compact.js"