ワンクリックで
test
Build, lint, and run tests to verify the implementation. Fourth step of the contribution workflow, use after /implement.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Build, lint, and run tests to verify the implementation. Fourth step of the contribution workflow, use after /implement.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | test |
| description | Build, lint, and run tests to verify the implementation. Fourth step of the contribution workflow, use after /implement. |
| disable-model-invocation | true |
| allowed-tools | Read Glob Grep Write Edit Bash |
| argument-hint | [additional context] |
| model | sonnet |
You are a QA engineer for the sfdx-hardis project.
Verify the implementation by building, linting, and running tests.
Related agent: this skill mirrors the
testsubagent (same process, also on Sonnet - running build/lint/test and fixing mechanical errors is medium-complexity work).
yarn compile to check TypeScript compilation.yarn lint to check for ESLint violations../bin/dev.js hardis:<category>:<action> [flags]
.js extensions in imports -> add themContinue fixing and re-running until all checks pass. Do not stop to ask whether to continue.
$ARGUMENTS
How to pick the correct uxLog level (action, log, warning, error, success, other), the matching chalk color, the options object (sensitive, alwaysVisible), VS Code UI suppression, and uxLogTable. Use when adding or modifying any uxLog call.
Style rules for updating CHANGELOG.md entries. Use whenever the user asks to update, add to, or write entries in CHANGELOG.md.
Gather requirements by asking clarifying questions until the problem is fully understood. First step of the contribution workflow.
Design the solution and write a technical specification based on requirements analysis. Second step of the contribution workflow, use after /analyze.
Handle CVE/vulnerability reports from security linters (trivy, osv-scanner, etc.). Tries to upgrade first; ignores only when safe and justified.
Implement a feature, bug fix, or code change in sfdx-hardis. Use whenever the user asks to add a feature, fix a bug, implement something, or make a code change - with or without a prior /design phase.