tdd

Estrellas0

Forks0

Actualizado2 de junio de 2026 a las 05:23

Vertical-slice test-driven workflow for meminsight features and fixes, anchored to OpenSpec capabilities and fixture validation.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

rdkcentral

rdkcentral/meminsight

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	tdd
description	Vertical-slice test-driven workflow for meminsight features and fixes, anchored to OpenSpec capabilities and fixture validation.

TDD

Purpose

Build changes in thin, behavior-first slices:

Write one failing behavior check.
Implement minimum code to pass.
Refactor safely.
Repeat.

Meminsight-specific rules

Start each slice from an OpenSpec capability in openspec/specs.
For parser/report changes, use fixture-based checks in test/ and test/run_ut.sh.
Avoid implementation-coupled tests when behavior-level checks are possible.
Preserve existing CSV structure unless explicitly changing behavior.
Validate optional JSON behavior where feature flags or schema are touched.

Slice template

Capability: C01 (example)
Behavior under test: short statement
Failing proof: command or test path
Minimal implementation change: files touched
Passing proof: command or test path

Exit criteria

All new behavior is linked to a capability spec.
Tests fail before and pass after implementation.
No unrelated behavior drift introduced.

Más de este repositorio

mismo repositorio

diagnose

rdkcentral/meminsight

Disciplined diagnosis loop for meminsight parser bugs, runtime failures, and regressions using deterministic fixture-first feedback.

2026-06-020

grill-with-docs-openspec

rdkcentral/meminsight

Structured requirement interview for larger changes, grounded in OpenSpec capabilities and repository constraints.

2026-06-020

openspec-source-of-truth

rdkcentral/meminsight

Use for implementation tasks to enforce OpenSpec-first behavior, As-Is alignment, and change-spec gating for behavior changes.

2026-06-020

to-issues-openspec

rdkcentral/meminsight

Break plans into implementation issues linked directly to OpenSpec capability IDs and acceptance checks.

2026-06-020

zoom-out

rdkcentral/meminsight

Provide a system-level map of meminsight modules, call flow, and capability ownership for onboarding and design clarity.

2026-06-020

proc-fragmentation-compat

rdkcentral/meminsight

Use when implementing or reviewing pagetypeinfo/buddyinfo collection with format drift tolerance, fallback behavior, and low-overhead parsing.

2026-04-230

name	tdd
description	Vertical-slice test-driven workflow for meminsight features and fixes, anchored to OpenSpec capabilities and fixture validation.

TDD

Purpose

Build changes in thin, behavior-first slices:

Write one failing behavior check.
Implement minimum code to pass.
Refactor safely.
Repeat.

Meminsight-specific rules

Start each slice from an OpenSpec capability in openspec/specs.
For parser/report changes, use fixture-based checks in test/ and test/run_ut.sh.
Avoid implementation-coupled tests when behavior-level checks are possible.
Preserve existing CSV structure unless explicitly changing behavior.
Validate optional JSON behavior where feature flags or schema are touched.

Slice template

Capability: C01 (example)
Behavior under test: short statement
Failing proof: command or test path
Minimal implementation change: files touched
Passing proof: command or test path

Exit criteria

All new behavior is linked to a capability spec.
Tests fail before and pass after implementation.
No unrelated behavior drift introduced.