scruffydan
14 verified skills
git-push
You MUST use this when performing a git push. Pre-push checklist for README updates, tests/linters, commit hygiene, secret scanning, and branch/remote status. Use when preparing to run git push, reviewing a branch before publishing, or verifying release readiness.
development
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
development
five-whys
Conduct root cause analysis using the Five Whys technique. Use when investigating problems, debugging issues, understanding failures, analyzing churn, or finding the underlying cause of any issue.
development
git-commit
Git commit workflow that analyzes recent history to match repo-specific message conventions. Use when you don't have recent commit history in context and need to determine the repository's commit message style, or when crafting commit messages that need to match existing conventions.
testing
using-docs-fetcher
How to use @docs-fetcher to pull current, targeted external documentation (APIs, SDKs, configs, errors, version changes). Use when you need authoritative docs or examples instead of relying on memory.
development
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
development
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
development
update-readme
Use when making code changes that affect user-facing behavior, before committing or pushing - reminds AI to check if README needs updates to stay in sync with implementation changes
development
using-code-review
How and when to invoke code review agents (@code-security, @code-readability, @code-performance, @code-redundancy, @code-simplifier, @code-full-review). Use before major PRs, audits, refactors, or whenever targeted review feedback is needed.
development
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
development
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
data-ai
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
testing
source/skills/implementation-workflow
--- name: implementation-workflow description: Six-phase implementation method for complex work: requirements, architecture, strategy, QA, security, optimization. Use for multi-step features, refactors, or high-risk changes that need structured planning and verification. --- # Implementation Workflow This document outlines the systematic approach for implementing complex technical solutions. ## Implementation Methodology ### 1. Requirements Analysis **Deep understanding of technical specific
development