Back to authors
samjhecht

samjhecht

46 Skills published on GitHub.

testing-anti-patterns

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

UncategorizedView skill →

testing-skills-with-subagents

DEPRECATED - Use writing-skills instead. This skill has been consolidated into writing-skills which now contains both skill creation and testing methodology.

UncategorizedView skill →

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

UncategorizedView skill →

using-wrangler

Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists

UncategorizedView skill →

validating-roadmap

Validates specification consistency, identifies implementation gaps, reviews roadmap coherence. Ensures documentation aligns, tasks are realistic, and dependencies are clear.

UncategorizedView skill →

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

UncategorizedView skill →

verify-governance

Verify integrity and completeness of governance framework - checks all required files exist, are properly formatted, have current metrics, and align with each other

UncategorizedView skill →

writing-plans

Use when design is complete and you need detailed implementation tasks - creates tracked MCP issues with exact file paths, complete code examples, and verification steps. Optional reference plan file for architecture overview.

UncategorizedView skill →

writing-skills

Use when creating new skills, editing existing skills, testing skills with pressure scenarios, or verifying skills work before deployment - applies TDD to process documentation by running baseline tests, writing minimal skill, and closing loopholes until bulletproof against rationalization

UncategorizedView skill →

writing-specifications

Use when creating technical specifications for features, systems, or architectural designs. Creates comprehensive specification documents using the Wrangler MCP issue management system with proper structure and completeness checks.

UncategorizedView skill →

Page 3 of 3 · 46 results