メニュー
Use this when checking, linting, or formatting code with SLICC's `biome` shell command. Covers its ipk prerequisites, config discovery, check, lint, and format modes, exit codes, and plain or JSON reporters.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ai-ecoverse/slicc --skill biomeコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use this when the user wants to write a new skill, edit an existing one, or understand SLICC's skill system. Covers SKILL.md frontmatter (name, description, allowed-tools), how to write a description that triggers reliably, native `/workspace/skills/` vs compatibility `.agents/` / `.claude/skills/` discovery, and when to ship companion files like `.jsh` scripts or `.bsh` browser hooks.
Use when committing, pushing, opening or updating a PR, or when CI fails on lint, typecheck, build, or coverage. Covers the full verification pass (lint → typecheck → test → coverage → build), lint:ci strictness, the boy-scout debt gate (check-touched-exemptions.mjs — complexity, promise safety, and ui back-edges; not part of npm run lint, easy to miss locally), and coverage floors. Also triggered by CI error strings like 'check-touched-exemptions' failure, 'biome found errors', or 'below configured minimum coverage'.
Use this when investigating memory pressure, suspected leaks, or out-of-memory crashes in the SLICC runtime (kernel worker, realms, WASM commands like vpod/ffmpeg/python3). Covers the `meminfo` shell command, how to read its breakdown, and its isolation prerequisite.
SOC 職業分類に基づく
SKILL.md を表示中
| name | biome |
| description | Use this when checking, linting, or formatting code with SLICC's `biome` shell command. Covers its ipk prerequisites, config discovery, check, lint, and format modes, exit codes, and plain or JSON reporters. |
| allowed-tools | bash |
Use the biome shell command for Biome checks inside the VFS. It is a thin wrapper over ipk-installed WASM packages, not a bundled Biome binary.
Install all three backing packages before linting or formatting:
ipk add @biomejs/wasm-web @biomejs/js-api esbuild-wasm
There is no CDN fallback. If a package is missing, follow the pinned ipk add command printed by biome --help or the error message.
| Command | Behavior |
|---|---|
biome check <files...> | Lint and check formatting. Add --write to apply formatting. |
biome lint <files...> | Lint only; never writes files. |
biome format <file> | Print formatted source. Add --write to update files. |
biome format --check <files...> | Report unformatted files without printing or writing changes. |
format --write and format --check are mutually exclusive. For piped input, pass --stdin-file-path <path> so Biome selects the correct parser.
Use --config-path <file> to select a config explicitly. Otherwise, discovery starts at the first target file's directory, or the current directory for stdin, and walks toward /. At each directory, biome.json takes precedence over biome.jsonc.
The wrapper accepts comments and trailing commas. It does not resolve extends.
The default plain reporter emits diagnostics as plain text without HTML entities, HTML tags, or added ANSI escapes.
Use --reporter json or --json for one JSON document on stdout with summary, diagnostics, and files fields. JSON diagnostic text is not written to stderr, and selecting JSON does not change the exit code.
| Code | Meaning |
|---|---|
0 | No findings, and checked files are formatted. |
1 | Error, fatal, or warning diagnostics; unformatted checked files; missing packages/files; or invalid discovered config. |
2 | Usage error, including a missing or invalid explicit --config-path. |
Treat code 1 as a failed check even when Biome reports only warnings.