Invocation

Syntax: /skill:snap-forge [branch[=name]] [worktree[=path]]

Args

Key	Values	Default	Notes
`help`	bool	false	show usage
`branch`	bool/text	false	`branch` derives a branch name; `branch=name` uses `name`
`worktree`	bool/text	false	`worktree` derives a worktree path/branch; `worktree=path` uses `path`

Test-Driven Development

Philosophy

Core principle: Tests should verify meaningful behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't.

Good tests are integration-style: they exercise real code paths through public APIs. They describe what the system does, not how it does it. A good test reads like a specification - "user can checkout with valid cart" tells you exactly what capability exists. These tests survive refactors because they don't care about internal structure. Write tests because the behavior is important, risky, or complex; do not add low-value tests just to raise coverage.