- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/claude-code-workflows --skill testing-principles -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/claude-code-workflows --skill testing-principles -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/claude-code-workflows --skill testing-principles -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/claude-code-workflows --skill testing-principles -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/shinpr/claude-code-workflows/tree/HEAD/dev-skills/skills/testing-principlesDel publicador
Tests here guarantee accepted behavior, and the next agent reads every existing test as a requirement to preserve. A brittle, duplicated, or implementation-shaped test therefore becomes a false requirement: it gets worked around, and the workaround leaves debt in the implementation. Keep the set of tests whose proof is worth its maintenance.
Mock-based tests are sufficient when data access is only a dependency of the behavior under test. Verify against the project's real database engine or its accepted equivalent when the subject is a query, repository implementation, schema constraint, or migration compatibility. Resolve the test environment from repository configuration; when no representative environment exists and adding one is outside the approved work, report the missing verification decision.
Cross-check data-access code against the schema source named in the Design Doc or repository configuration. Schema-source verification is required to prove table, column, type, constraint, or dialect compatibility; successful mocks prove behavior only at the mocked boundary.
A capability probe passes when it uses the consumer's boundary and asserts the exact property that consumer needs. Command success, import success, or object existence is setup evidence.
Follow the repository's established test paths, runner routing, and naming. When establishing an approved new convention, separate test types only when their setup, runner, or environment differs.
Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, including frontend and browser E2E tests. Use when writing tests, deciding test scope,
---name: testing-principlesdescription: Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof…---# dev-skills/skills/testing-principles/SKILL.mdResumen general
Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, including frontend and browser E2E tests. Use when writing tests, deciding test scope, or reviewing test quality.
Preguntas frecuentes
Descarga dev-skills/skills/testing-principles/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/shinpr/claude-code-workflows.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.