test-from-spec

Estrelas19

Forks0

Atualizado16 de maio de 2026 às 18:40

Use when a ReAuth feature spec already exists and you need to add, tighten, or verify tests against that spec. This skill maps the spec's test scenarios to the current implementation, uses Graphify before broad architecture scanning when graphify-out/graph.json exists, and adds the smallest effective tests at the right layer.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

sagargupta2001

sagargupta2001/ReAuth

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

Explorador de arquivos

2 arquivos

SKILL.md

readonly

Mais deste repositório

mesmo repositório

docs-sync-after-change

sagargupta2001/ReAuth

Use after ReAuth code or docs changes to keep specs, memory docs, indexes, and Graphify state aligned. This skill inspects the diff, applies the update rules from docs/agent/08-documentation-system.md, uses Graphify before broad architecture scanning when graphify-out/graph.json exists, and runs docs validation.

2026-05-1619

implement-from-spec

sagargupta2001/ReAuth

Use when a ReAuth feature already has a spec in docs/specs and the next step is implementation. This skill reads the spec, the matching agent and memory docs, uses Graphify before broad architecture scanning when graphify-out/graph.json exists, and implements the smallest coherent vertical slice with tests.

2026-05-1619

spec-from-requirement

sagargupta2001/ReAuth

Use when a user has a rough feature requirement, ticket, or product note and wants a ReAuth spec created or updated under docs/specs. This skill turns ambiguous requirements into implementation-ready specs by reading the repo docs, checking for existing specs first, and using Graphify before broad architecture scanning when graphify-out/graph.json exists.

2026-05-1619

name	test-from-spec
description	Use when a ReAuth feature spec already exists and you need to add, tighten, or verify tests against that spec. This skill maps the spec's test scenarios to the current implementation, uses Graphify before broad architecture scanning when graphify-out/graph.json exists, and adds the smallest effective tests at the right layer.

Test From Spec

Overview

Add or verify test coverage directly from a ReAuth spec. Use this after or during implementation when the code exists but the acceptance coverage is incomplete or unclear.

Workflow

Read AGENTS.md, docs/agent/05-testing.md, docs/agent/07-spec-driven-delivery.md, and the target spec in docs/specs/.
Use the spec's Test Scenarios as the expected behavior contract.
Inspect the current implementation and existing tests before writing new ones.
If architecture or codebase context is needed and graphify-out/graph.json exists:
- compare the commit recorded in graphify-out/GRAPH_REPORT.md with git rev-parse HEAD
- run graphify query, graphify explain, or graphify path before broad repo scanning
Choose the smallest effective layer:
- unit for domain or service rules
- integration for API, repository, and cross-module behavior
- UI tests for feature flows, forms, and route-driven behavior
Add or update only the missing coverage needed by the spec.
Run make docs-check and the narrowest relevant verification commands.

Coverage Expectations

Happy path.
Validation failure.
Business rule edge case.
Failure or recovery path when the spec defines one.

Guardrails

Do not invent behaviors that are not in the spec.
If code and spec conflict, report the gap instead of hiding it behind tests.
Prefer adding the smallest effective tests over broad suite rewrites.