Run the project's validation pipeline (lint → format → typecheck → unit tests) with auto-fixes, then optionally stage and write a Conventional Commit. Use before committing, when asked to "check", "validate", "run the workflow", or "get this commit-ready".
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Mode: $0 (default full). Optional commit message: the remaining arguments.
!git status --short
!git diff --stat HEAD
Run in order and stop at the first step that still fails after auto-fixing. Report each step as ✓ or ✗ with file:line references.
pnpm lint:fix. If errors remain, fix them in code (don't disable rules without a comment explaining why) and re-run.pnpm format (Prettier: JSON/MD/YAML/CSS only; TS/Vue have no formatter, so match surrounding style).pnpm typecheck. Fix type errors properly: no any, as unknown as, or @ts-ignore unless an existing pattern requires it.quick mode. Otherwise run pnpm vitest run <files> for the test files that mirror changed sources first (fast feedback), then pnpm test./run-app for local verification or pnpm test:e2e:smoke.commit mode only):
git diff and stage only files that belong to this change (git add <paths>, not git add -A blindly).<type>(<scope>): <lowercase subject>, header ≤ 100 chars, types feat fix docs style refactor perf test build ci chore revert, scopes such as editor preview ai tools learn store api types test seo deps ci. Use ! for breaking changes. Explain why in the body when it isn't obvious.--no-verify.master.End with a short summary: which steps ran, what was auto-fixed, anything still failing, and the commit hash if one was created.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add, update, or retire an AI provider model option for the BYOK theme generator (OpenAI, Anthropic, Google) and verify the provider requests native structured output for it. Use when model lists go stale or a new provider/model is requested.
日本語の概要は準備中です。原文の説明を表示しています。
Add a new interactive design tool under /tools (like the color converter or contrast checker) — component, page, navigation, route lists, SEO, and tests. Use when building a new utility tool.
日本語の概要は準備中です。原文の説明を表示しています。
Write and register a new Learning Hub article (Nuxt Content markdown under content/learn) with valid frontmatter, navigation entry, route list entry, and accurate product details. Use when adding or substantially rewriting a learn guide, reference, or tip.
日本語の概要は準備中です。原文の説明を表示しています。
Add a new component showcase, block, or template preview page and register it everywhere it must appear (navigation, command palette, route lists, SEO, source view). Use when adding anything under /components, /blocks, or /templates.
日本語の概要は準備中です。原文の説明を表示しています。
Checklist for adding or changing a field on ThemeConfig (a new design token, per-mode setting, or export option) end to end — schema, defaults, store + history, CSS apply, export, editor UI, AI, and tests. Use whenever ThemeConfig's shape changes.
日本語の概要は準備中です。原文の説明を表示しています。
Audit websites for SEO, performance, security, technical, content, and 15 other issue cateories with 230+ rules using the squirrelscan CLI. Returns LLM-optimized reports with health scores, broken links, meta tag analysis, and actionable recommendations. Use to discover and asses website or webapp issues and health.
日本語の概要は準備中です。原文の説明を表示しています。