CodingCossack

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Collaborative 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.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Dispatches 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.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Git branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Assesses 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.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Use 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.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Sequential 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…

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Git worktree–based workspace isolation for parallel or non-disruptive development. Use when work must occur without modifying or interfering with the current working tree.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Meta-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.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Verification 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.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.

CodingCossack/agent-skills-library

Skill Claude CodeCodex

Use when creating new skills, editing existing skills, or verifying skills work before deployment.

CodingCossack/tanstack-start-rsc-skill

Skill Codex

Implement, review, debug, and refactor TanStack Start React Server Components in React 19 apps. Use when tasks mention @tanstack/react-start/rsc, renderServerComponent, createCompositeComponent, CompositeComponent, renderToReadableStream, createFromReadableStream, createFromFetch, Composite Components, React Flight…

CodingCossack/change-with-proof

Skill Codex

Use when changing software whose existing behaviour matters — fixing bugs or regressions, refactoring, migrating schemas or APIs, changing auth, payments, webhooks, persistence, or user-visible behaviour, removing code, resuming inherited work — and when reviewing such changes or judging whether they are done. Every…