Menú
Use for implementing production-grade Syngen features or non-trivial code changes.
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.
Basado en la clasificación ocupacional SOC
Use to verify or set up the local Syngen development environment — creates a `.venv` if missing, installs `requirements.txt`, probes runtime imports, and confirms pytest collection works. Invoke this on a fresh checkout, when pytest reports `ModuleNotFoundError`, or when `python -m build / twine / mypy` says the tool is not installed.
Use for selecting the correct test, lint, CI, or packaging command for a given Syngen change.
Use when a coding or testing session reveals that a harness file (rule, skill, agent, or doc) is inaccurate, incomplete, or blocking correct work. Requires human approval before any harness file is changed.
Use for marshmallow validation errors, metadata schema failures, and CLI argument validation issues in Syngen.
| name | syngen-implement-feature |
| description | Use for implementing production-grade Syngen features or non-trivial code changes. |
Use the names defined in docs/agent-harness/glossary.md (business / product, plus the metadata-YAML keys). If a draft uses an undefined term, add it to the glossary in the same change rather than inventing a synonym.
python -m … command reports ModuleNotFoundError, invoke the syngen-bootstrap skill before continuing. The harness fixed a structural collection break on 2026-05-27 by adding src/tests/__init__.py and a [tool.pytest.ini_options] block in pyproject.toml; runtime deps from requirements.txt may still be missing locally.src/syngen/, tests under src/tests/unit/, examples in examples/, demo notebooks, CI configuration.train, infer, syngen — note these are the binary names; launch_train / launch_infer are the function names), [[SDK]] (Syngen class in src/syngen/sdk.py), [[metadata YAML]] schema, or serialization format. Any break is an [[escalation trigger]].src/tests/unit/, plus integration tests if CLI / file I/O / metadata execution is affected).syngen.ml.src/syngen/VERSION — semver patch by default; minor when public API or CLI changes; major requires APPROVAL REQUIRED: and explicit approved per the contract.testing-contract.md:
cd "$(git rev-parse --show-toplevel)"):
PY="${REPO_ROOT}/.venv/bin/python"; test -x "${PY}" || PY="$(command -v python)"
"${PY}" -m pytest src/tests/unit/<touched_subpath> -q
"${PY}" -m flake8 --max-line-length 99 src/syngen/<touched_subpath>
"${PY}" -m pytest src/tests/unit/ -q # full unit suite before handoff
ModuleNotFoundError, run syngen-bootstrap once and retry.syngen-code-reviewer for non-trivial code changes; syngen-test-engineer if test coverage needs review; syngen-security-reviewer for any change touching encryption, credentials, data flow, or logging.