一键在 Manus 中运行任何 Skill

test

星标359

分支98

更新时间2026年6月13日 13:28

Build, lint, and run tests to verify the implementation. Fourth step of the contribution workflow, use after /implement.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

hardisgroupcom

hardisgroupcom/sfdx-hardis

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Process

Compile: Run yarn compile to check TypeScript compilation.
Lint: Run yarn lint to check for ESLint violations.
Fix issues: If compilation or linting fails, fix the errors and re-run.
Test locally: If the change involves a command, test it with:
```
./bin/dev.js hardis:<category>:<action> [flags]
```
Report results: Summarize what passed and what failed.

Common Issues

Missing .js extensions in imports -> add them
i18n keys not in all locale files -> add missing keys
Type errors -> fix TypeScript types
Lint errors -> follow ESLint rules

Continue fixing and re-running until all checks pass. Do not stop to ask whether to continue.

$ARGUMENTS

同仓库更多 Skills

同仓库

uxlog-usage

hardisgroupcom/sfdx-hardis

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.

2026-07-07359

changelog

hardisgroupcom/sfdx-hardis

Style rules for updating CHANGELOG.md entries. Use whenever the user asks to update, add to, or write entries in CHANGELOG.md.

2026-06-21359

analyze

hardisgroupcom/sfdx-hardis

Gather requirements by asking clarifying questions until the problem is fully understood. First step of the contribution workflow.

2026-06-14359

design

hardisgroupcom/sfdx-hardis

Design the solution and write a technical specification based on requirements analysis. Second step of the contribution workflow, use after /analyze.

2026-06-13359

fix-security-issue

hardisgroupcom/sfdx-hardis

Handle CVE/vulnerability reports from security linters (trivy, osv-scanner, etc.). Tries to upgrade first; ignores only when safe and justified.

2026-06-13359

implement

hardisgroupcom/sfdx-hardis

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.

2026-06-13359

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 test subagent (same process, also on Sonnet - running build/lint/test and fixing mechanical errors is medium-complexity work).

Process

Compile: Run yarn compile to check TypeScript compilation.
Lint: Run yarn lint to check for ESLint violations.
Fix issues: If compilation or linting fails, fix the errors and re-run.
Test locally: If the change involves a command, test it with:
```
./bin/dev.js hardis:<category>:<action> [flags]
```
Report results: Summarize what passed and what failed.

Common Issues

Missing .js extensions in imports -> add them
i18n keys not in all locale files -> add missing keys
Type errors -> fix TypeScript types
Lint errors -> follow ESLint rules

Continue fixing and re-running until all checks pass. Do not stop to ask whether to continue.

$ARGUMENTS