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

validate

スター0

フォーク0

更新日2026年2月6日 14:49

Run post-feature validation checks on the codebase. Use when (1) user says /validate, "validate", "run checks", "verify build", "run validation", (2) after implementing any feature or code change, (3) before committing code, (4) when user wants to ensure nothing is broken. Runs tests, build, type-check, lint, and unused code detection in sequence.

インストール

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

Manusで実行

ソース

jaqubowsky

jaqubowsky/jobZ

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

ダウンロード

Manusで実行

Post-Feature Validation

Run all five validation steps in sequence, stopping on first failure:

pnpm run test && pnpm run build && pnpm run check-types && pnpm run lint && pnpm run knip

Execution

Run the command above
If any step fails, stop and report which step failed with the error output
If all steps pass, report success

Output Format

On success:

All checks passed:
  - test
  - build
  - check-types
  - lint
  - knip

On failure, report the failing step and its error output so the user can fix it. Do NOT continue to subsequent steps after a failure.

このリポジトリの他の Skills

同じリポジトリ

update-docs

jaqubowsky/jobZ

Keep project documentation fresh after codebase changes. Use PROACTIVELY at the END of any implementation task that changes the codebase, specifically after (1) database migrations or schema changes — add/drop columns, tables, enums, functions, (2) changing package exports or public APIs, (3) adding/removing/renaming features, components, or routes, (4) modifying scraping strategies or adding job boards, (5) changing environment variables or configuration, (6) any structural change that could make existing CLAUDE.md or MEMORY.md docs stale. Trigger AFTER code changes are complete but BEFORE committing.

2026-02-090

post-task-simplify

jaqubowsky/jobZ

Automatically run the code-simplifier agent on recently modified code after completing any implementation task. This skill should be triggered at the end of any feature development, bug fix, refactoring, code migration, or similar coding task — essentially whenever code has been written or modified as part of the current conversation. It should NOT be triggered for research-only tasks, documentation questions, or conversations where no code was changed.

2026-02-090

regression-test

jaqubowsky/jobZ

Create regression tests for reported bugs to prevent them from recurring. Use when (1) user reports a bug and asks to write tests, (2) user says "write regression test", "add test for this bug", "make sure this never happens again", "test this fix", (3) after fixing a bug to ensure it stays fixed, (4) user describes a scenario that broke and wants test coverage.

2026-02-090

new-server-action

jaqubowsky/jobZ

Scaffold a new server action with optional mapper and types. Use when (1) user says /new-server-action, "create server action", "add server action", "new action", "scaffold action", (2) adding a new API endpoint to a feature, (3) creating a new data-fetching or mutation function for a feature. Generates files following the project's Result type, type decoupling, and mapper patterns.

2026-02-060

feature-consistency

jaqubowsky/jobZ

Ensures feature structure consistency and co-location patterns in the web app. Use when (1) creating new features like auth, bookmarks, notifications, (2) editing existing features - adding/modifying components, hooks, utils, types, or schemas, (3) reviewing feature structure for compliance, (4) refactoring to co-locate component-specific logic, (5) adding new components with hooks or utilities. Examples of user requests that should trigger this skill include "add a new feature", "create component with hook", "add form to dashboard", "refactor profile feature", "check feature structure".

2026-02-050

create-migration

jaqubowsky/jobZ

Creates Supabase migration files with proper naming, structure, and best practices. Use when (1) user wants to create a new database migration, (2) adding/modifying tables, columns, or constraints, (3) adding indexes for performance, (4) setting up Row Level Security (RLS) policies, (5) creating triggers or functions, (6) any database schema changes. Example requests include "create migration", "add table for bookmarks", "add column to users", "set up RLS", "create database trigger".

2026-02-050

name	validate
description	Run post-feature validation checks on the codebase. Use when (1) user says /validate, "validate", "run checks", "verify build", "run validation", (2) after implementing any feature or code change, (3) before committing code, (4) when user wants to ensure nothing is broken. Runs tests, build, type-check, lint, and unused code detection in sequence.

Post-Feature Validation

Run all five validation steps in sequence, stopping on first failure:

pnpm run test && pnpm run build && pnpm run check-types && pnpm run lint && pnpm run knip

Execution

Run the command above
If any step fails, stop and report which step failed with the error output
If all steps pass, report success

Output Format

On success:

All checks passed:
  - test
  - build
  - check-types
  - lint
  - knip

On failure, report the failing step and its error output so the user can fix it. Do NOT continue to subsequent steps after a failure.