「file」の検索結果

input/files内のファイルを読み込んで企画案を作成するコマンド

Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).

日本語の概要は準備中です。原文の説明を表示しています。

Dockerfile / Containerfile / compose analysis plus optional Trivy / Grype / Syft composition when those binaries are present. Use when reviewing a Dockerfile PR, gating `docker build`, building an image SBOM, evaluating base-image risk, or auditing a registry image for CVEs.

日本語の概要は準備中です。原文の説明を表示しています。

Produce a coverage & quality profile of a Narrative dataset (or access rule): row count, per-column null/fill rate, cardinality, ranges, top-values, inferred column shape, and quality flags. Reads bundled stats + sample first, recovers missing/stale stats by configuring and recalculating them, and escalates to a cheap `/write-nql` query only for a measure no stat can provide. Descriptive, not prescriptive. Use when: "profile dataset N", "what does dataset N look like", "coverage and quality of <dataset>", "what id types does N emit", "null rates / cardinality for <dataset>", "is this dataset's stats fresh". (narrative-common)

日本語の概要は準備中です。原文の説明を表示しています。

Systematically explore an unfamiliar codebase and build a reusable architecture summary. Use for repo onboarding, understanding legacy or inherited code, mapping architecture before a migration or refactor, tracing a bug or feature path, or answering "what does this project do?". Documentation-first, then data flow — ends in a concise technical architecture summary with file:line evidence, not a raw file dump.

日本語の概要は準備中です。原文の説明を表示しています。

Two-phase code quality skill: (1) review codebase for structural smells — file LOC, method LOC, accidental complexity, test readability — producing a structured report, then (2) fix all smells via provable refactorings with ACN micro commits and green-bar-at-all-times discipline. Use this skill when the user says 'sweep', 'code review', 'find code smells', 'check method lengths', 'review for complexity', 'tidy up the codebase', 'refactor smells', or asks about long methods, test readability, or accidental complexity. Also trigger when users ask to 'clean up' or 'improve code quality' across multiple files.

日本語の概要は準備中です。原文の説明を表示しています。

Brutally honest AGENTS.md/CLAUDE.md review backed by real A/B test evidence. Not just opinions — actual proof that your rules are dead weight. Roasts instruction files for bloat, slop, and redundancy, then proves it by running evals. Use when user says "roast my agents.md", "roast my CLAUDE.md", "prove my rules are useless", "eval roast", or wants entertaining evidence-based feedback on their AI config files. Also triggers on "audit my instructions" or "are my rules helping".

日本語の概要は準備中です。原文の説明を表示しています。

基于 glob 通配符模式的批量文件操作（删除、移动、复制、列表）。用于高效文件系统操作的 CLI 工具。零依赖。

日本語の概要は準備中です。原文の説明を表示しています。

globパターンを使用したバッチファイル操作（削除、移動、コピー、一覧表示）。効率的なファイルシステム操作のためのCLIツール。依存関係なし。

Пакетные операции с файлами (удаление, перемещение, копирование, список) с использованием масок glob. CLI-инструмент для эффективной работы с файловой системой. Без зависимостей.

日本語の概要は準備中です。原文の説明を表示しています。

Operaciones de archivos en lote (delete, move, copy, list) con patrones glob. Herramienta CLI para operaciones eficientes en el sistema de archivos. Sin dependencias.

日本語の概要は準備中です。原文の説明を表示しています。

Batch-Dateioperationen (Löschen, Verschieben, Kopieren, Auflisten) mit Glob-Mustern. CLI-Werkzeug für effiziente Dateisystem-Operationen. Ohne Abhängigkeiten.

日本語の概要は準備中です。原文の説明を表示しています。

Evolutionary file renaming with wrapper files, plus the terse MOVED-stub standard for whole folder/file moves. Enables renames without hard breaks — references are organically updated through usage.

日本語の概要は準備中です。原文の説明を表示しています。

Work with SuperCollider projects as files - the shape of a .scd piece, how to read and write one with sc_project, how to send the file that is on disk into the live session with sc_load, what state belongs in the session and what belongs in the file, and how to package a piece the SuperCollider way (a folder with its .scd, its SynthDefs, and a Quark-style layout) instead of inventing a format.

日本語の概要は準備中です。原文の説明を表示しています。

指定した起動ディレクトリとdotfiles rootのスキル配置・エージェント定義を、既存audit scriptで点検する。

Dockerfile、Compose、Terraform、GitHub Actionsをread-only検査し、共通Finding schemaとredaction基準で返す。

指定した起動ディレクトリと、親が確定した dotfiles root のスキル配置・エージェント定義を点検する。 判定の正は etc/audit-skill-agent-layout.py。実効 runtime の native 優先順、Cursor の name、 agent の model/role、生成物の状態を報告する。「overlay 点検」「スキル配置」 「エージェント定義は共通か」「layout audit」「/overlay-audit」で使う。

Dockerfile・Compose・Terraform・GitHub Actionsの差分または指定パスをread-onlyで検査し、共通Finding schemaとredaction基準で結果を返す。ユーザーが `/sentinel-review` と入力したら必ず使う。

- Extract and interpret embedded file metadata with exiftool — EXIF GPS coordinates, camera make, model and serial, DateTimeOriginal and CreateDate timestamps, XMP and IPTC fields, and Office and PDF… Use when reading EXIF from a photo, checking who really wrote a document, dating a file, fingerprinting a camera or phone, or investigating provenance in JPEG, HEIC, RAW, MP4, DOCX, XLSX or PDF

日本語の概要は準備中です。原文の説明を表示しています。

Scaffolds and reviews the main entry-point PHP file of a WordPress plugin — header (with Requires Plugins for WP 6.5+), ABSPATH guard, file/path/url/version constants, Composer + PSR-4 with manual spl_autoload_register fallback, register_activation_hook requirements check, Plugin class instantiation on plugins_loaded, and the WP 6.7+ rule that translation functions must not trigger before after_setup_theme. Use when scaffolding a new plugin or reviewing its main file. Triggers on Plugin Name headers, register_activation_hook, Requires Plugins, spl_autoload_register, plugins_loaded, or composer.json at the plugin root.

日本語の概要は準備中です。原文の説明を表示しています。

Audits WordPress plugin or theme PHP code for the most common security mistakes — missing nonce checks, capability checks, input sanitization, output escaping, unslashing, SQL preparation, AJAX nopriv exposure, file/path traversal, and unsafe redirects. Use when reviewing pull requests, before releasing a plugin, when the user asks "is this secure", or when handling code that touches $_GET / $_POST / $_REQUEST / $_COOKIE / $_FILES / $_SERVER, admin-ajax / admin-post, REST endpoints, options, user meta, custom DB queries, or file uploads.

日本語の概要は準備中です。原文の説明を表示しています。

敵対的分析手法を統合したレビューの entry skill。認知バイアス対策の3手法 （Pre-mortem / War Game / Logic Torturing）と、宣言・主張と実態の乖離を突く claim-vs-actual 検出3パターン（Self-Contradiction / Refactor-Claim Audit / Cross-File Leakage）へルーティングし、通常のレビューでは見えない設計の盲点・ 防御の穴・論理の弱点・宣言と実装のズレを可視化する。

Creates and reviews agent skills safely by enforcing deletion-prevention harness rules: no fixed absolute temp paths, no cwd-dependent cleanup, no wildcard deletes, no workspace-external file operations, no silent cleanup failures, and mandatory temp-root validation before any destructive command. Use when creating a new skill, updating an existing SKILL.md, or reviewing prompts/runbooks that include temp files, extraction, cleanup, PowerShell, bash, rm, del, Remove-Item, or archive expansion.

日本語の概要は準備中です。原文の説明を表示しています。

Enforces project coding standards during code review: naming conventions (PascalCase for classes, camelCase for methods/variables, UPPER_SNAKE_CASE for constants, kebab-case for files), standard file structure, anti-magic-number policy, file size limits (500/800 lines), security patterns, and design patterns. Use when reviewing code, writing new code, or checking adherence to project conventions.

日本語の概要は準備中です。原文の説明を表示しています。