Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
npx claudepluginhub kastheco/claude-plugins --plugin kasComplete the current session by ensuring all work is committed and pushed.
Finalize and merge a pull request after work is complete and approved.
Run code review using kas-code-reviewer agent
Review implementation plan using plan-reviewer agent
Run reality assessment using project-reality-manager agent
Browser automation specialist for web testing, scraping, and interaction. Use this agent when you need to interact with web pages, test UIs, capture screenshots, or automate browser workflows. Handles all Claude-in-Chrome MCP operations.
Use this agent when you need a ruthless code review channeling Linus Torvalds philosophy. This agent performs rigorous review with zero tolerance for mediocrity, focusing on correctness, simplicity, performance, readability, and robust error handling. <example> Context: User has made code changes and wants review. user: "Review my recent changes" assistant: "I'll launch the kas-code-reviewer agent for a thorough review." <commentary> User explicitly requested code review. Trigger kas-code-reviewer agent. </commentary> </example> <example> Context: User is about to commit code. user: "Check this code before I commit" assistant: "Let me run the kas-code-reviewer agent to catch issues." <commentary> Pre-commit review request. Proactively trigger code review. </commentary> </example> <example> Context: User wants staged files reviewed. user: "Code review the staged files" assistant: "I'll use the kas-code-reviewer agent to review the staged changes." <commentary> Staged files review request. Invoke kas-code-reviewer. </commentary> </example>
Use this agent when you need to review an implementation plan for security gaps, design flaws, or missing tests before execution. This agent should be invoked PROACTIVELY whenever a plan is ready for user approval - run the review BEFORE asking the user to approve the plan. <example> Context: User just created an implementation plan. user: "Review this plan for security gaps and design issues" assistant: "I'll launch the plan-reviewer agent to evaluate the plan." <commentary> User explicitly requested plan review. Invoke plan-reviewer agent. </commentary> </example> <example> Context: Assistant just finished writing a plan to a plan file in plan mode. user: [No new message - assistant proactively reviews] assistant: "I've written the plan. Let me run the plan-reviewer agent to check for issues before asking for your approval." <commentary> Plan file was just written. PROACTIVELY invoke plan-reviewer BEFORE calling ExitPlanMode or asking user to approve. This ensures plans are reviewed automatically. </commentary> </example> <example> Context: Assistant is about to call ExitPlanMode to request plan approval. user: [No new message - assistant proactively reviews] assistant: "Before requesting approval, let me run the plan-reviewer agent to ensure the plan is solid." <commentary> About to exit plan mode. MUST invoke plan-reviewer proactively before ExitPlanMode. Never ask for plan approval without running review first. </commentary> </example>
Use this agent when you need to validate claimed task completions, assess the actual functional state of implementations, or create pragmatic plans to complete work that may have been marked done prematurely. This agent excels at cutting through optimistic status reports to identify what truly works versus what merely exists in code. <example> Context: User suspects claimed work might be incomplete. user: "Verify if this feature actually works" assistant: "I'll use the project-reality-manager to validate the actual state." <commentary> Completion validation request. Trigger project-reality-manager. </commentary> </example> <example> Context: Task was marked complete but seems broken. user: "Check if this is really done" assistant: "Let me run the project-reality-manager to assess what truly works." <commentary> Skeptical completion check. Invoke project-reality-manager. </commentary> </example> <example> Context: User wants to audit progress on a feature. user: "What's the actual state of the authentication feature?" assistant: "I'll use the project-reality-manager to cut through status reports and assess reality." <commentary> Reality assessment request. Trigger project-reality-manager. </commentary> </example>
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Installer for TÂCHES' Get-Shit-Done workflow system - meta-prompting, context engineering and spec-driven development
Commands for orchestrating complex workflows
Core planning and workflow infrastructure for the Claudikins ecosystem
Task orchestrator for Claude Code — spawn and manage multiple task sessions
Corca Workflow Framework — consolidated hooks and skill orchestration for structured development sessions
Task orchestration using Claude Code's built-in task tools with slash commands for importing plans and executing tasks individually, sequentially, or with a team
ClickUp task management with kas workflow integration
A marketplace of Claude Code plugins for workflow automation, task tracking, and code review.
| Plugin | Description | Version |
|---|---|---|
| kas | Workflow automation with beads task tracking, session management, and code review | 1.7.0 |
# Add marketplace
claude plugin marketplace add brkastner/kas-claude-plugins
# List available plugins
claude plugin marketplace list kas-claude-plugins
# Install kas plugin
claude plugin install kas@kas-claude-plugins
# Clone the repo
git clone https://github.com/brkastner/kas-claude-plugins.git
# Use specific plugin with Claude Code
claude --plugin-dir ./plugins/kas
Each plugin has its own README with detailed usage instructions:
See CONTRIBUTING.md for guidelines on adding new plugins.
MIT