ワンクリックでManusで任意のスキルを実行

始める

validate-changes

スター4

フォーク1

更新日2026年6月24日 21:24

Guidelines and instructions for validating code modifications by running lint, build, and test suites via Nx.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

daveteply

daveteply/job-tracker

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Validate Changes with Nx

This skill provides guidelines and practices to ensure the workspace health is verified after any code modifications.

1. Core Principles

Validate after changes: After any file edit, creation, or deletion, you must ensure the integrity of the workspace.
Run comprehensive checks: Always run linting, building, and testing targets across all projects.
Address failures immediately: If any workspace target fails, locate the failing project/file and resolve the error before continuing or declaring the task done.

2. Validation Command

Execute the following command in the workspace root:

npx nx run-many -t lint build test

Targets Run:

lint: Asserts style guides, imports order, syntax safety, and rules (including any minimization).
build: Builds production artifacts for Next.js app (web-ui) and TypeScript backend (sync-backend) to check for compiler errors.
test: Runs unit and integration test suites using Vitest and Jest to verify logical correctness.

3. Automation Hook

[!NOTE] The automated PostToolUse command hook is disabled to prevent executing commands outside the dev container environment. Changes must be validated manually from within the dev container.

このリポジトリの他の Skills

同じリポジトリ

backend-workflow

daveteply/job-tracker

Guidelines and information on backend architecture (Node.js, Fastify, Prisma 7), database client configuration, and starting the development server.

2026-06-234

beta-management

daveteply/job-tracker

Guidelines and instructions for administrative tasks, including approving beta users and disabling user synchronization.

2026-06-234

minimize-any

daveteply/job-tracker

Guideline and instructions for reducing and avoiding the use of 'any' in TypeScript codebase, and properly annotating acceptable usages with eslint-disable comments.

2026-06-234

optimize-heroicons

daveteply/job-tracker

Guidelines and instructions for using direct imports for Heroicons in the frontend to maintain a small bundle size and ensure tree-shaking.

2026-06-234

name	validate-changes
description	Guidelines and instructions for validating code modifications by running lint, build, and test suites via Nx.

Validate Changes with Nx

This skill provides guidelines and practices to ensure the workspace health is verified after any code modifications.

1. Core Principles

Validate after changes: After any file edit, creation, or deletion, you must ensure the integrity of the workspace.
Run comprehensive checks: Always run linting, building, and testing targets across all projects.
Address failures immediately: If any workspace target fails, locate the failing project/file and resolve the error before continuing or declaring the task done.

2. Validation Command

Execute the following command in the workspace root:

npx nx run-many -t lint build test

Targets Run:

lint: Asserts style guides, imports order, syntax safety, and rules (including any minimization).
build: Builds production artifacts for Next.js app (web-ui) and TypeScript backend (sync-backend) to check for compiler errors.
test: Runs unit and integration test suites using Vitest and Jest to verify logical correctness.

3. Automation Hook

[!NOTE] The automated PostToolUse command hook is disabled to prevent executing commands outside the dev container environment. Changes must be validated manually from within the dev container.