Explore skills

Enforce a strict Gitflow-based workflow with conventional commits, semantic versioning, and issue-driven branching. Applies to git operations like committing, branching, merging, releasing, or when terms like 'gitflow' or 'semver' are mentioned.

FlowMem generates a Mermaid-based AI memory system for any codebase, library, or documentation set. Knowledge is stored as human-readable .mmd files, viewable in VS Code or browsers, and traversable by AI coding assistants.

Use when reviewing an AI-generated implementation plan before execution, when handed a plan to approve, or when checking if a plan is ready to act on.

Use with any AI SDK or API (Anthropic, OpenAI, Google) to fetch real-time documentation, preventing bugs from outdated training data. It triggers on model selection, tool use, function calling, streaming, prompt caching, batch processing, SDK setup, or any AI API integration, planning, debugging, or code review.

Multi-agent context bridge — seamlessly switch between AI coding agents without losing context.

Use when asked to review a PR, or when /review is invoked with a PR number or URL. Performs a focused code review checking for bugs, security, performance, and test gaps, then posts findings as a PR comment and formal GitHub review.

Guide for testing practices and frameworks.

Plan and execute large multi-step, multi-stack changes with contract-first waves, parallel worker ownership, user approval gates, ordered integration, and final verification/docs updates using Claude Code Agent subagents. Use only when the task spans multiple areas (for example frontend, backend, tests, errors, docs) or has dependency-heavy sequencing.

Plan and execute large multi-step, multi-stack changes with contract-first waves, parallel worker ownership, user approval gates, ordered integration, and final verification/docs updates. Use only when the task spans multiple areas (for example frontend, backend, tests, errors, docs) or has dependency-heavy sequencing.

Plan and execute large multi-step, multi-stack changes with contract-first waves, parallel worker ownership, user approval gates, ordered integration, and final verification/docs updates through acpx. Use this when you explicitly want cross-CLI or cross-provider workers instead of Codex subagents.

[PM Twin] Generate product status update from recent activity — git history, feature progress, metrics.

Sharpen vague intentions into clear intent cards through Socratic questioning with a separate Clarity Judge agent.