메뉴
Test-phase skill for pi-forge. Use during the Test phase to run the project's test suites (unit, integration, contract, E2E for the general path), capture results and coverage, write artifacts/test-report.md, and record metrics via forge_metric.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | tester |
| description | Test-phase skill for pi-forge. Use during the Test phase to run the project's test suites (unit, integration, contract, E2E for the general path), capture results and coverage, write artifacts/test-report.md, and record metrics via forge_metric. |
Run the project's tests and report results. General path only (CXAS evals are handled elsewhere). Drive transitions only through forge_* tools.
artifacts/test-report.md summarizing what ran, results, failures (with the actual output), and coverage.forge_metric test {"passRate": <0..1>, "coverage": <0..1 or null>, "suites": {...}}.forge_artifact test_report artifacts/test-report.md.Use the cxas-wrapper skill / forge_cxas:
forge_cxas with subcommand: "lint", args: ["--app-dir", "<dir>", "--json"]; record error/warning counts.forge_cxas with subcommand: "run", args: ["--app-name", "<resource>", "--wait"] (exit 0 pass / 1 fail).
Fold both into artifacts/test-report.md and forge_metric test {"cxas": {"lint": {...}, "eval": {...}}}.Safe bridge to the cxas CLI for pi-forge CXAS projects. Use whenever a CX Agent Studio project needs to lint an app directory, run evaluations, manage apps/deployments, or migrate from Dialogflow CX. Always go through the forge_cxas tool (never raw shell); it enforces an allow-list and returns structured results.
Evaluate-phase skill for pi-forge. Use during the Evaluate phase to make a holistic, freeform judgment of the work against the brief, write artifacts/scorecard.md with an approve|iterate recommendation plus justification and risks, and record the verdict via forge_metric to inform the G2 gate.
First Build-phase skill for pi-forge. Use at the start of the Build phase to turn the approved brief into an executable plan. Reads artifacts/brief.json and writes artifacts/plan.md with the approach, module/feature breakdown (WBS), build sequence, and stack rationale.
Drives a project through the pi-forge delivery lifecycle (intake → clarify → build → test → evaluate → improve → deliver). Use when starting or continuing a pi-forge project, or whenever asked to "run the project", "continue the project", or after /forge-new. Reads state via forge_status and advances phases via forge_advance, opening gates with forge_gate.
Improve-phase skill for pi-forge. Use during the Improve phase after an iterate verdict to root-cause the scorecard findings, write a prioritized artifacts/backlog.md, and hand back so the orchestrator re-enters the Build phase (bounded by maxIterations).
Clarify-phase skill for pi-forge. Use during the Clarify phase to turn a raw request into a high-quality Project Brief. Scans for ambiguity across functional, non-functional, integration, data, user, edge-case, metric, and scope dimensions, asks batched categorized questions, and writes artifacts/brief.md + brief.json.