# Nexent Test Assets

Create and maintain Nexent's repository-owned feature catalog, D1-D5 case-local...

- Repository: https://github.com/ModelEngine-Group/nexent (6109 stars)
- Category: Documents
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ModelEngine-Group/nexent --skill nexent-test-assets -g -a claude-code -y`
Codex: `npx skills add ModelEngine-Group/nexent --skill nexent-test-assets -g -a codex -y`
Cursor: `npx skills add ModelEngine-Group/nexent --skill nexent-test-assets -g -a cursor -y`
Gemini CLI: `npx skills add ModelEngine-Group/nexent --skill nexent-test-assets -g -a gemini-cli -y`

## Description

Create and maintain Nexent's repository-owned feature catalog, D1-D5 case-local contracts and fixed scripts, change records, generated execution registry and Excel view. Use for requirements, bug regressions, post-development test backfill, test implementation, and formal asset migration. Traditional UT uses nexent-python-tests.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Nexent formal test assets

Maintain one traceable chain:

`Requirement or Bug -> Feature -> D1-D5 Case -> case-local execution.yaml -> Fixed Script -> Result`.

Paths are relative to the repository root. Authoritative assets live under `test-e2e/features/<Feature-ID>/feature.yaml`, `test-e2e/cases/<Case-ID>/case.yaml`, and `test-e2e/changes/<type>/`. Each implemented Case owns `execution.yaml` and its primary test script in the same Case directory. `features/<Feature-ID>/cases.md`, `test-e2e/infra/generated/registry.json`, and the Excel workbook there are generated read-only views; no hand-maintained central manifest or cross-platform symlink is needed.

## Boundaries

The rest: https://github.com/ModelEngine-Group/nexent/blob/HEAD/.agents/skills/nexent-test-assets/SKILL.md