sharp-testing
From the author
Rules for writing valuable automated tests without accumulating redundant or implementation-coupled checks. Read before implementing features, fixing bugs, refactoring, or writing and changing tests.
Install
npx skills add paleo/alignfirst --skill sharp-testing -a claude-code
Installs to .claude/skills/sharp-testing/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- write-testsdzhng/skillsWrite tests that pin real behavior instead of implementation details, config values, or lucky samples. Use when adding tests for new behavior, writing a regression test, fixing a brittle or flaky test, reviewing a test diff, or when a test breaks after a refactor or config change that didn't change behavior.Testing★ 1.4K
- sharp-writingpaleo/alignfirstConventions for writing sharp, concise prose and Markdown, for human readers and AI agents. Read before writing or editing documentation, READMEs, instructions, agent skills, or any prose text.Writing★ 86
- Testing CodeMicrock/ordinary-claude-skillsWrite automated tests for features, validate functionality against acceptance criteria, and ensure code coverage. Use when writing test code, verifying functionality, or adding test coverage to existing code.Testing★ 408
- spec-writingathola/claude-night-marketCreates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning.Writing★ 343
- test-strategynahid-sparktales/agent-dispatcherDecide what to test and at which level before any tests get written — enumerate failure modes by consequence, give each one the cheapest level that can actually observe it, and name what is deliberately left uncovered. Use when starting testing on a feature or a codebase, when asked for a test plan or why coverage sits where it does, or when a suite is large and still missing bugs. Not for writing the tests themselves, and not for proving a finished change works.Testing★ 59
- test-driven-developmentmvschwarz/openrigUse when implementing any feature or bugfix, before writing implementation codeTesting★ 8.2K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in