workflow-tools

Plugin workflow-tools from marketplace santos in denisraison/claude-plugins. Commands read from the repo's manifest — 19 days ago.

Skills (8)

• code-cleanup

  This skill should be used when the user asks to "clean up tests", "clean up code", "tidy up tests", "remove dead tests", "organize test files", "fix test structure", or mentions test hygiene, test bloat, removing temporary tests, or following test best practices. Unlike the code-review skill (which

• diagnose

  This skill should be used when the user says "diagnose this", "debug this", "why is this failing", "this is broken", "track down this bug", or reports something throwing, crashing, returning wrong output, or a performance regression. A disciplined diagnosis loop for hard bugs: build a feedback loop,

• fix-comments

  Review code comments in a diff and remove or trim AI slop, bloat, and noise, keeping only comments that earn their place. Use when the user says "review the comments", "remove slop comments", "deslop the branch", "trim the comments", "do we need this comment", "we added too many comments", "can we c

• code-refactor

  This skill should be used when the user asks to "refactor this package", "reorganize this code", "split this file", "this code is a mess", "too many files", "simplify this module", "restructure this", or mentions god structs, god components, god classes, package organization, module structure, or co

• code-review

  Reviews code changes for quality issues. Use when user says "review my changes", "review the diff", "review my code", "check for issues", "sanity check", or asks to find holes, gaps, or simplification opportunities.

• self-evaluating

  This skill should be used when creating or editing documents, diagrams, handover docs, PEPs, or any substantial written output. Also activates when the user says "evaluate this", "run in a loop until good", "rate this out of 10", "is this 10/10", "loop until fixed", "keep improving", or asks for ite

• trim-context

  Trim CLAUDE.md and AGENTS.md files to reduce context cost. Apply the "less is more" finding from empirical research on agentic coding context files. Use when user says "trim our context files", "lean up CLAUDE.md", "optimize our agents.md", "reduce context", "our CLAUDE.md is too long", or asks to a

• writing-naturally

  This skill should be used when writing documentation, PR descriptions, handover docs, PEPs, Confluence pages, or any prose output. Activates when the user asks to "write a document", "create a handover", "update the docs", "write a PR description", "draft a PEP", or any task producing written conten

Slash commands (1)

• /workflow-tools:catchup

  Restore context after /clear - shows git state and active PEPs

Subagents (2)

• browser-tester

  Use this agent when the user wants to visually check, test, or debug frontend changes in a browser. This agent uses claude-in-chrome to see the page, interact with elements, and read console logs.

• gate-keeper

  Use this agent when the user wants to verify that a PEP wave is complete, validate gate criteria, or get a confidence-scored evaluation of implementation progress. This agent reads the PEP, checks the diff, evaluates gate criteria, and produces a structured verdict.

Similar plugins