All authors

Claude Skills by CodingCossack
github.com/CodingCossack14 skills0 installs11 views
- BrainstormingCollaborative design exploration that refines ideas into validated specs through iterative questioning. Use before any creative work including creating features, building components, adding functionality, or modifying behavior.Votes: 0GitHub stars: 19
- Dispatching Parallel AgentsDispatches one subagent per independent domain to parallelize investigation/fixes. Use when you have 2+ unrelated failures (e.g., separate failing test files, subsystems, bugs) with no shared state or ordering dependencies.Votes: 0GitHub stars: 19
- Executing PlansDisciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.Votes: 0GitHub stars: 19
- Finishing A Development BranchGit branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.Votes: 0GitHub stars: 19
- Receiving Code ReviewAssesses and responds to incoming code review feedback on PRs (reviewer comments, requested changes), especially when suggestions are unclear, technically questionable, or scope-expanding. Use before implementing review suggestions to align on intent and keep changes minimal.Votes: 0GitHub stars: 19
- Requesting Code ReviewUse when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.Votes: 0GitHub stars: 19
- Subagent Driven DevelopmentSequential subagent execution with two-stage review gates for implementation plans. Use when executing multi-task plans in current session, when tasks need fresh subagent context to avoid pollution, when formal review cycles (spec compliance then code quality) are required between tasks, or when you need diff-based validation of each task before proceeding.Votes: 0GitHub stars: 19
- Systematic DebuggingRoot cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.Votes: 0GitHub stars: 19
- Test Driven DevelopmentRed-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.Votes: 0GitHub stars: 19
- Using Git WorktreesGit worktree–based workspace isolation for parallel or non-disruptive development. Use when work must occur without modifying or interfering with the current working tree.Votes: 0GitHub stars: 19
- Using SuperpowersMeta-skill enforcing skill discovery and invocation discipline through mandatory workflows. Use when starting any conversation to check for relevant skills before any response, ensuring skill-first workflow before proceeding.Votes: 0GitHub stars: 19
- Verification Before CompletionVerification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.Votes: 0GitHub stars: 19
- Writing PlansStructured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.Votes: 0GitHub stars: 19
- Writing SkillsUse when creating new skills, editing existing skills, or verifying skills work before deploymentVotes: 0GitHub stars: 19