testing
sefaertunc/anthropic-watch/.claude/skills/testing/SKILL.md
Test philosophy, coverage strategy, test-first patterns, what to test and what not to
Often used withbundle-dependency-prsupdate-library-template
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
sefaertunc/anthropic-watch/.claude/skills/testing/SKILL.md
Test philosophy, coverage strategy, test-first patterns, what to test and what not to
Often used withbundle-dependency-prsupdate-library-template
susomejias/skills/testing/SKILL.md
Pragmatic testing guidance focused on confidence, behavior over implementation details, and integration-first coverage. Use when designing a test strategy, writing or reviewing tests, reducing brittle mocks, or deciding what is worth testing in an application or library.
Often used withbundle-dependency-prsupdate-library-template
tiago-oliveira-ca/zenodotus-harness/skills/testing/SKILL.md
Software testing documentation dispatcher. Use when creating, reviewing, or improving test specifications and test documentation. Trigger on: "write test cases", "create a test plan", "test specification", "STS", "TDS", "TCS", "TPS", "test procedure", "define exit criteria", "requirements traceability matrix", "RTM", "risk-based testing", "test environment", "non-functional testing", "accessibility testing", "security testing", "performance testing", "CI/CD test integration", "document how to test this feature", "IEEE 829", or any task producing or reviewing software test documentation.
Often used withbundle-dependency-prsupdate-library-template
tslateman/skills/skills/craft/testing/SKILL.md
Design test strategy using Beck's Test Desiderata — which properties matter, which tradeoffs to make. Use when the user asks "how should I test this", "what tests do I need", "review my test strategy", "is this well-tested", or when planning tests for a new feature or refactor.
Often used withbundle-dependency-prsupdate-library-template
zmievsa/skills/skills/testing/SKILL.md
Use any time you need to test anything or write tests for anything, including bug reproduction, test reviews, regression coverage, etc.
Often used withbundle-dependency-prsupdate-library-template
anthropics/knowledge-work-plugins/finance/skills/sox-testing/SKILL.md
Generate SOX sample selections, testing workpapers, and control assessments. Use when planning quarterly or annual SOX 404 testing, pulling a sample for a control (revenue, P2P, ITGC, close), building a testing workpaper template, or evaluating and classifying a control deficiency.
Steady6 mentions in 2 weeks
1 project uses a version of this
vincelwt/gloomberb/.agents/skills/tui-testing/SKILL.md
Testing Gloomberb at every level: CLI commands for fast data/integration checks, OpenTUI's built-in test harness for component tests, and tmux for full end-to-end terminal TUI testing. Use this skill when you need to verify terminal TUI features, write OpenTUI regression tests, or smoke-test the terminal app. Do not use it for Electrobun/desktop-web-only visual or window chrome work unless tmux/OpenTUI coverage is explicitly needed.
Gentleman-Programming/Gentleman.Dots/skills/go-testing/SKILL.md
Go testing patterns for Gentleman.Dots, including Bubbletea TUI testing. Trigger: When writing Go tests, using teatest, or adding test coverage.
krayin/laravel-crm/.github/skills/pest-testing/SKILL.md
Use when writing or updating Krayin CRM tests (unit or feature), debugging test failures, using datasets, mocks or custom expectations, writing architecture tests, or when the user mentions test, spec, TDD, expects, assertion, or coverage. Uses the Pest PHP framework (v3) with Laravel 12.
Often used withlivewire-developmenttailwindcss-developmentlaravel-best-practices
2bTwist/dotagents/skills/testing/SKILL.md
Test a change across the surfaces it touches, not only the path just written. Use when starting non-trivial implementation (claims, case grid, seams), when that work is built (attack the grid, keep few durable tests), when fixing a reported defect, and when judging an existing suite. Skip for one-line fixes with an obvious cause, copy or colour changes, and renames.
Often used withbundle-dependency-prsupdate-library-template
aazirani/flutter_agentify/.agents/skills/testing/SKILL.md
Which kind of test to write for which kind of change, and the helpers this repo gives you. Use when adding or changing an action, repository, screen, assistant behavior or database migration, or when a test fails.
Often used withbundle-dependency-prsupdate-library-template
alfredobs97/flutter_agentic_template/.agents/skills/testing/SKILL.md
Covers the testing pattern for every layer — domain (package:test with a hand-written Fake data provider, no mocktail), data (an ephemeral real instance or a mocked client), ui Cubit/BLoC (blocTest + mocktail against the domain repository), ui widgets (the pumpApp helper), and router tests (a fresh buildAppRouter() per test); triggers whenever a test is being written for a new entity, provider, repository, Cubit/BLoC, widget, or route.
Often used withbundle-dependency-prsupdate-library-template
alumpe/skills/testing/SKILL.md
Guides which automated tests are worth writing and how to write them well. Use when deciding whether code needs tests or when creating, modifying, or reviewing automated tests.
Often used withbundle-dependency-prsupdate-library-template
anipy1/claude-flutter-kit/.claude/skills/testing/SKILL.md
Unit, bloc, widget, and integration testing conventions — bloc_test, mocktail, http_mock_adapter, test naming, and what to test. Use when writing or fixing any test, mocking a dependency, or deciding what tests a change requires.
Often used withbundle-dependency-prsupdate-library-template
anurag-azure/skills/testing/SKILL.md
Application test strategy: unit, slice, and integration testing; coverage targets; test data; mocking discipline. Framework resolved from the TSA.
Often used withbundle-dependency-prsupdate-library-template
bmarshall511/Trellis/.claude/skills/testing/SKILL.md
Use when writing tests, deciding what to test, reviewing test coverage, or verifying that a spec's acceptance criteria are actually covered. Also when a test is failing and the fix is unclear.
Often used withbundle-dependency-prsupdate-library-template
bubbleviki404/app-development-skills/skills/testing/SKILL.md
Coverage-driven, discovery-first product testing that operates a real app across risk-driven sessions and multi-session campaigns, maintains complementary product-surface and risk-dimension coverage, uncovers unreported bugs, and independently verifies fixes without changing production code. Use for Quick Exploration, Delta Discovery, systematic Full Discovery Campaigns, Final Broad Testing, Fix Verification / Regression after Builder implementation, Maestro-assisted flows, hardware/device coverage planning, or proactive testing beyond existing unit/UI suites.
Often used withbundle-dependency-prsupdate-library-template
cachewraith/cachewraith-skills/skills/testing/SKILL.md
Run, write, and debug tests — unit, integration, and end-to-end — in whatever framework the project already uses (Jest, Vitest, PHPUnit, Pytest, Go test, cargo test, RSpec, JUnit). Invoke when the user asks to test something, run the suite, add or fix tests, check coverage, or investigate a failing test. Skip when they want a code review rather than tests, or are asking how a test framework works in the abstract.
Often used withbundle-dependency-prsupdate-library-template
davidmarcombes/skills/skills/python/testing/skill.md
skill_name: pytest_testing_guide version: 1.0.0 tags: [testing, pytest, quality, tdd] --- # Pytest Testing Guide ## Core Principles 1. **Use pytest exclusively** - not unittest or nose 2. **Organize tests by concern
Often used withbundle-dependency-prsupdate-library-template
dewitt4/claude-code-template/.claude/skills/testing/SKILL.md
Generate comprehensive test cases, improve test coverage, and create testing strategies for unit, integration, and e2e tests
Often used withbundle-dependency-prsupdate-library-template
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.