askill
CodingCossack

CodingCossack

Publisher on askill

65 total stars
Skills12
Updated 1/3/2026
GitHub
executing-plans
executing-plans
CodingCossack1/3/2026

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

17
AI 89
finishing-a-development-branch
finishing-a-development-branch
CodingCossack1/3/2026

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.

8
AI 93
dispatching-parallel-agents
dispatching-parallel-agents
CodingCossack1/3/2026

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

8
AI 92
verification-before-completion
verification-before-completion
CodingCossack1/3/2026

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.

8
AI 87
subagent-driven-development
subagent-driven-development
CodingCossack1/3/2026

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, w...

8
requesting-code-review
requesting-code-review
CodingCossack1/3/2026

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.

8
systematic-debugging
systematic-debugging
CodingCossack1/3/2026

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

8
finishing-a-development-branch
finishing-a-development-branch
CodingCossack12/22/2025

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.

0
AI 96
verification-before-completion
verification-before-completion
CodingCossack12/22/2025

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.

0
AI 92
subagent-driven-development
subagent-driven-development
CodingCossack12/22/2025

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, w...

0
AI 86
dispatching-parallel-agents
dispatching-parallel-agents
CodingCossack12/22/2025

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

0
AI 84
requesting-code-review
requesting-code-review
CodingCossack12/22/2025

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.

0
Showing all 12 skills.