David McInnis
Community@mcinnisd
David McInnis publishes user-invoked software engineering skills covering test-driven development, systematic debugging, code review, git worktrees, and codebase auditing.
Agent Skills by David McInnis
Showing 16 vetted skills indexed across 1 GitHub repositories.
using-git-worktrees
Creates isolated git worktree workspaces with detection, setup, and baseline test verification.
deep-test
Prunes redundant tests and detects critical coverage gaps through multi-phase test suite auditing.
deep-audit
Audits codebases for architectural alignment, deduplication, and widget contract integrity with human review.
test-driven-development
Enforces red-green-refactor test-driven development workflow for writing code with failing tests first.
systematic-debugging
Diagnose software bugs through a four-phase root cause investigation process.
using-superpowers
Guides discretionary invocation of superpowers skills across AI coding harnesses.
dispatching-parallel-agents
Dispatch concurrent subagents to investigate independent test failures across separate problem domains.
executing-plans
Executes implementation plans task by task with verification and blocker escalation.
finishing-a-development-branch
Guides merging, pushing, or preserving a completed development branch after verifying tests.
brainstorming
Guides collaborative dialogue to turn ideas into approved design specs.
writing-plans
Writes detailed implementation plans with bite-sized TDD tasks and exact file paths.
requesting-code-review
Dispatch a code reviewer subagent to evaluate git diffs against requirements.
receiving-code-review
Guides AI agents to verify, evaluate, and implement code review feedback with technical reasoning.
writing-skills
Create and test agent skills using test-driven development with pressure scenarios.
verification-before-completion
Enforces running verification commands before claiming task completion or success.
subagent-driven-development
Executes implementation plans by dispatching fresh subagents per task with per-task and final code reviews.
Frequently Asked Questions About David McInnis
FAQPage SchemaWhat tasks can I perform using David McInnis's skills?▼
You can practice test-driven development, debug systematically, brainstorm ideas into specs, write and execute implementation plans, dispatch parallel subagents, request and receive code reviews, audit codebases for duplication and architectural drift, prune bloated test suites, and verify work before completion.
Who are these skills designed for?▼
Software engineers and development teams who follow disciplined engineering practices. The skills target practitioners doing test-driven development, structured debugging, code review cycles, branch management with git worktrees, and large-scale codebase audits requiring architectural alignment and issue tracking.
How are these skills invoked at runtime?▼
Every skill in the manifest is user-invoked, with disable-model-invocation set to true in the native frontmatter. This means they never trigger automatically; the developer explicitly calls each skill, such as deep-test, deep-audit, or systematic-debugging, when needed during a session.
What is the deep-test skill and how does it differ from deep-audit?▼
Deep-test performs a dual mandate: deleting redundant or tautological tests while finding critical coverage gaps to fix or ticket, then executing tests dynamically and creating issues. Deep-audit instead reviews the whole codebase for architectural alignment, deduplication, and widget/schema integrity.
What prerequisites or dependencies do these skills require?▼
The manifest specifies no external dependencies, runtimes, or paid services. Skills rely on a standard git-based development environment for worktrees and branch finishing, plus issue tracking integration referenced as Wayfinder/GitHub issues for the deep-audit and deep-test capabilities.