popkit-dev

work #N | brainstorm | plan | execute | prd | suite | "description" [--mode quick|full] [--provider auto|popkit|feature-dev] [-T, --power]

commit | push | pr | review | ci | release | publish | prune | finish [--draft, --squash]

create | list | view | close | comment | edit | link [--state, --label]

list | create | close | report | health [--json, --verbose]

[quick|verbose] - Analyze project state and recommend next actions

morning | nightly [run|quick|generate|list|set|edit|delete]

list | create | remove | switch | update-all | prune | init | analyze

Designs feature architectures and implementation blueprints based on codebase patterns. Use during architecture phase when multiple implementation approaches exist and trade-offs need evaluation.

Deeply analyzes existing codebase features by tracing execution paths, data flow, and dependencies. Use during exploration phase of feature development or when understanding unfamiliar code.

Performs comprehensive code reviews focusing on TypeScript, React, and Node.js best practices. Use after implementing significant features or when code quality assessment is needed.

Code restructuring specialist focused on improving quality, maintainability, and performance without changing external behavior. Use for code smell detection, design pattern application, and systematic codebase improvements.

AI-powered merge conflict resolution with complexity-based prioritization and architectural intelligence. Detects conflicts, analyzes complexity, prioritizes resolution order, proposes intelligent fixes with reasoning, validates changes with tests. Use when git merge fails with conflicts.

AI-powered merge conflict resolution with complexity-based prioritization and architectural intelligence.

Transforms Product Requirements Documents into structured, actionable tasks with automatic complexity analysis and technology research. Parses markdown PRDs, extracts features, scores complexity, researches technologies, and generates implementation roadmap.

**High Priority Quick Win** - Demonstrates seamless PopKit feature integration

Fast MVP development specialist for quick proof-of-concept implementations. Use when building prototypes, validating ideas, or creating minimal viable features quickly.

Collaborative design refinement that transforms rough ideas into fully-formed specifications through Socratic questioning. Explores alternatives, validates incrementally, and presents designs in digestible chunks for feedback. Use before writing code or implementation plans when requirements are unclear or multiple approaches exist. Do NOT use when requirements are already well-defined, you're implementing a known pattern, or making small changes - proceed directly to implementation instead.

Enhanced changelog generation with semantic versioning, auto-categorization, and release notes. Parses conventional commits, determines version bump (MAJOR.MINOR.PATCH), categorizes changes by type, generates CHANGELOG.md updates, and creates GitHub release notes. Use before releases or on PR merge to automate version management.

Analyzes task/feature complexity (1-10) and recommends subtask breakdown for planning and prioritization. Provides actionable recommendations for agent selection, phase distribution, and risk assessment. Silent analysis that feeds into other workflows.

Use when you need to fully restore working context from a previous session - loads STATUS.json, reads key files, rebuilds mental model of current work state. Do NOT use for quick questions or when starting fresh unrelated work - the full context restoration adds overhead that isn't needed for standalone tasks.

Controlled batch execution of implementation plans with review checkpoints between phases. Loads plan, critically reviews for issues, executes tasks in batches, then pauses for architect feedback before continuing. Use when you have a complete implementation plan from brainstorming/writing-plans and want structured execution with quality gates. Do NOT use for ad-hoc implementation, exploratory coding, or when you don't have a formal plan - just implement directly with code review at the end.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup. Presents exactly 4 options: merge locally, create PR, keep as-is, or discard. Do NOT use when tests are failing or work is incomplete - fix issues first before finishing the branch.

Start-of-day setup and readiness routine. Calculates Ready to Code Score (0-100) based on session restoration, service health, dependency updates, branch sync, PR reviews, and issue triage. Automatically captures session state to STATUS.json. Use at start of work day after opening Claude Code.

Context-aware recommendation engine that analyzes git status, TypeScript errors, GitHub issues, and technical debt to suggest prioritized next actions. Returns specific popkit commands with explanations of why each is relevant. Use when unsure what to work on next, starting a session, or feeling stuck. Do NOT use when you already know what to do - just proceed with that task directly.

End-of-day cleanup and maintenance routine. Calculates Sleep Score (0-100) based on uncommitted work, branch cleanup, issue updates, CI status, and service shutdown. Automatically captures session state to STATUS.json. Use at end of work day before closing Claude Code.

Display routine measurement dashboard with metrics, costs, trends, and visualization

Token-optimized morning/nightly routine using caching and selective execution

Create, switch, and merge session branches for side investigations. Branch off to explore bugs, research APIs, or debug issues without polluting main context. Use when you need to temporarily focus on something different, then return to your main work.

Saves complete session state to STATUS.json for seamless continuation across conversations. Captures git context, in-progress tasks, service status, focus area, and next actions. Use at the end of work sessions, before context limits, or when switching to a different task. Do NOT use mid-task or for quick questions - the overhead is only worthwhile when you actually need to resume later.

Use at start of new session to restore context from STATUS.json - loads previous state, displays session type, shows what to continue working on. Calculates session type (Continuation/Resume/Fresh Start) based on time gap. Do NOT use mid-session or when starting fresh work unrelated to previous session - just begin the new task directly.

Python-based git worktree manager with 8 operations: list, create, remove, switch, update-all, prune, init, analyze. Handles cross-platform paths, STATUS.json integration, protected branch safety. Use this skill when the user invokes /popkit-dev:worktree command or needs programmatic worktree management.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification. Verifies .gitignore, runs project setup, confirms clean test baseline. Do NOT use for quick fixes or small changes - worktrees add overhead; use simple branch switching for trivial changes.

Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context. Assumes skilled developers who need domain-specific guidance, following DRY, YAGNI, and TDD principles. Use after brainstorming/design is complete when handing off to another developer or planning complex multi-step work. Do NOT use for simple tasks, quick fixes, or when you're implementing yourself and already understand the codebase - just start coding instead.

1 hook across 1 event