메뉴
Start testing session with focused context. Use when beginning test workflows with the user-testing agent.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when manually generating or updating the canonical 3-workflow GitHub Actions CI/CD set (deploy.yml, provision.yml, post-merge-deploy.yml) for a Node.js + React application deployed to a VM via Terraform and Docker Compose. Also use when an operator invokes /cicd.generate, or when updating existing workflows to match project conventions. In `smaqit.new-greenfield-project`, the deployment agent generates workflows during Phase 5 using these patterns as reference — invoke this skill directly only when generating CI/CD outside the zero-to-prod flow. Note: `copilot-setup-steps.yml` is provided by the smaqit framework and is not generated by this skill.
Use when deploying a Node.js backend + React frontend application to a remote VM via rsync. Used in the Phase 5 dev environment sweep of `smaqit.new-greenfield-project` to validate the deployment approach locally before CI/CD. Also use as a manual fallback for direct VM deployment outside the CI/CD pipeline.
Use after any deployment to confirm the application is healthy before closing the task or proceeding. Checks the health endpoint, verifies the deployed commit SHA against the current local commit, and validates the SPA root HTTP response. Produces a PASS/FAIL report per check with a final summary. Also use when a deployment task asks to confirm success or when re-verifying after a fix.
Use when configuring a custom domain with a Let's Encrypt TLS certificate for a running nginx server. Covers DNS propagation verification, nginx server_name update, Certbot certificate issuance, HTTPS smoke tests, and auto-renewal verification. Also use when activating a purchased domain for a deployed application, setting up HTTPS post-deployment, or when a spec references INF-TOPOLOGY-004 through INF-TOPOLOGY-007 as pending TLS configuration.
Use when writing deploy stamp files (DEPLOY_SHA, DEPLOY_TIME) to the VM after a successful deployment, or when re-stamping without a full redeploy. Also use when the health endpoint returns "sha":"unknown" after deployment, when a deployed PR needs a notification comment, or when smaqit.infrastructure-deploy-rsync invokes the post-deploy stamp step. Produces DEPLOY_SHA and DEPLOY_TIME files in /opt/him/backend/ on the VM and optionally posts a deploy comment on the merged PR.
Use when validating staged files before committing to catch .env files, plaintext API keys/secrets, draft spec files on main-branch commits, and large files over 1 MB. Also use when setting up the automated git pre-commit hook via the bundled install script so checks run automatically on every commit. Produces a PASS/FAIL report per check, with filenames and matching lines listed for failures.
| name | smaqit.test-start |
| description | Start testing session with focused context. Use when beginning test workflows with the user-testing agent. |
| metadata | {"version":"0.3.0"} |
| agent | smaqit.user-testing |
Start a testing session with minimal, focused context. Loads project test entrypoints and (optionally) a specific test file only.
Execute these steps IN ORDER:
Read the project files that define how tests are run (whichever exist):
README.mdCONTRIBUTING.md and/or TESTING.mdMakefilepackage.json (scripts)pyproject.toml / tox.ini / pytest.inigo.mod (then infer go test ./...)Critical: Read complete files without truncation.
User must specify: Test number (e.g., "059")
Read the complete test file:
.smaqit/user-testing/tests/{TEST_NUMBER}_*.mdIf the test file does not exist, ask whether to create it under .smaqit/user-testing/tests/ before proceeding.
This file contains:
From the test file, identify:
Present a concise summary:
Then state: "Ready to begin test execution. Say 'start' to proceed."
Explicitly excluded to keep context focused:
.smaqit/history/*.md) - Not needed for test execution.smaqit/PLANNING.md) - Not needed during testMinimal focused context:
READ COMPLETE FILES: Do NOT truncate test entrypoint files or the test file.
MODE: You are now in test execution mode. Follow the test file workflow and your agent directives for execution philosophy, coordination patterns, and report generation.
Test start is successful when: