菜单
Run or inspect the relevant validation paths and turn failures, regressions, or missing coverage into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | test-codebase |
| description | Run or inspect the relevant validation paths and turn failures, regressions, or missing coverage into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting. |
Read these shared references when needed:
../shared/references/findings.schema.md../shared/references/findings.lifecycle.mdRun validation-oriented testing work and convert the result into findings.
Accept a depth parameter from the prompt:
shallowdeepDefault:
depth=deepAccept an optional path from the prompt.
path is provided, use it as the local design or findings folder.path is omitted, infer it from the branch, subsystem, or matching docs and state the inferred value before starting.Default:
path=inferEstablish validation scope. Confirm the effective variables first:
pathdepthChoose the validation surface. Use existing tests first when they are relevant. Add targeted repro or smoke execution when that is the shortest way to validate behavior.
Run or inspect. Execute the chosen tests or repro steps when possible. If execution is blocked, record the blocker and its impact explicitly.
Turn outcomes into findings. Capture broken behavior, flaky behavior, missing coverage, missing assertions, environment gaps, and rollout risks in the active findings record.
Update the active findings record.
Use path/findings.md.
Hand off when review or implementation is needed.
Use triage-findings for follow-up questions and planning.
Use resolve-findings when the intended fix path is clear.
Write PR titles and descriptions the way a staff engineer would. Use when drafting or editing a pull request title and body, before running `gh pr create`, or any time the user asks for a PR description, summary, or release-notes-style writeup of a change. Apply this skill from the start, not as a cleanup pass after a generic first draft.
Use this skill to create and publish changelog announcements for new features, improvements, or bug fixes. This skill handles the complete workflow - creating detailed changelog documentation pages, adding sidebar announcement cards, and ensuring everything follows project standards. Use when the user mentions adding changelog entries, documenting new features, creating release notes, or announcing product updates.
Where to put frontend code (package vs app layer) and how to use the @agenta/* packages. Use when authoring or moving code in web/packages, choosing between @agenta/ui, @agenta/entities, @agenta/entity-ui, @agenta/shared, @agenta/playground, using molecules, loadable/runnable bridges, the EntityPicker, or writing package unit tests.
Use when writing or editing documentation pages (concept pages, how-to guides, API reference prose, tutorials) under docs/. Provides the writing style, voice, and structural rules for Agenta docs. Apply this skill before drafting any new docs page, and include it in the brief for any subagent tasked with writing docs.
Audit and update the supported LLM model list in assets.py against litellm's registry (models.litellm.ai). Use when adding new models, pruning outdated ones, or verifying the list is correct.
Sync the findings record against local review artifacts and optionally a GitHub PR. Accept optional `path` and GitHub PR `url`; when `url` is provided, sync against both remote PR state and local state, otherwise default to local-only sync. Default to `path=infer`. Confirm effective variables before starting.