2,355 件 ・ 関連度順
概要と使いどころ
Use when picking which analysis or project-analysis-* skill fits a request — routes by scope, framework, and symptom — even if the user just says 'analyze this' or 'dig into the codebase'.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project contains HTML data tables (<table> elements). Under no circumstances use tables for layout purposes. Absolutely always include <th> elements with appropriate scope attributes, a <caption> or aria-labelledby, and ensure complex tables have headers associated with data cells. Apply these rules to every data table without exception.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when you need to run /workflow-review-changes repeatedly in an outer convergence loop until a complete whole-workflow run applies zero fixes — recursive re-review of a fixed scope (branch-diff + current changes) until a clean no-op pass.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when you need to perform a security review or audit on any scope — application code (OWASP Top 10 2025), secrets exposure, dependency/supply-chain malware, third-party repository vetting before install, infrastructure/config, CI/CD pipeline, AI-agent risks, and host/VPS compromise detection.
日本語の概要は準備中です。原文の説明を表示しています。
[Implementation] Use when you need to analyze and fix issues [INTELLIGENT ROUTING]. Flag: --target={ci|issue|logs|test|types|ui} scopes the fix; --target=types resolves TypeScript errors inline.
日本語の概要は準備中です。原文の説明を表示しています。
[Planning] Use when calibrating estimates from actual code, diff, PR scope, and developer time.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when you need to generate a step-by-step demo guide (demo script / walkthrough) covering all main user stories and their test cases — scope from a named feature, else the current working context, else confirm with the user — explaining for each case how the domain data is stored/changed and how the domain solves the feature. Triggers: demo guide, generate demo guide, demo script, demo walkthrough, how to demo, prepare demo, sprint demo, user story demo.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when you need to combine /changes-review + /fix in a recursive loop — each round runs /changes-review (report-only) to surface validated findings over a fixed diff scope, then /fix to resolve them, then loops again with a FRESH full /changes-review over the CHANGED diff until one complete pass produces zero validated findings (nothing left to fix).
日本語の概要は準備中です。原文の説明を表示しています。
[Architecture] Use when auditing the ENTIRE project architecture and production readiness in one pass — bundles architecture-review + architecture-scalability-review + production-readiness-review at project or diff scope, then synthesizes one consolidated Architecture Health Report.
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating a single dense technical architecture, reference poster, or system diagram image for a software project. Produces a source-grounded bitmap diagram with topology, primitives, ingest/process flow, core logic, state scopes, tiers/modules, surfaces, runtime cards, and strict semantic color rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use between coding-agent runs (Codex, Claude Code, Cursor, Aider, etc.) to stop the project from drifting, overbuilding, or accumulating dead weight. Forces a read-only audit that classifies every active item as KEEP / DELAY / REMOVE and ends with a single, unambiguous next action. Trigger on "audit before continuing", "what should I do next", "this project got too big", "between runs", "trim scope", "stop adding stuff", or any signal that the project feels noisy and the next step is unclear. Do NOT load for trivial one-line fixes, when the next action is already obvious, or when you're mid-run and just need to keep going.
日本語の概要は準備中です。原文の説明を表示しています。
Triage a GitHub issue that already has the cc-issue-created label and is assumed to be ready to start. First inspect the comment history to decide whether human confirmation is needed (cc-need-human-check, highest priority); otherwise decide whether the issue should be closed as not needed, unanswered confirmation items remain (cc-answer-issue-questions), the description is stale relative to settled comment-history content and must be refreshed before execution (cc-update-issue), or it can move to execution (cc-exec-issue). Dependency checks are out of scope.
日本語の概要は準備中です。原文の説明を表示しています。
Manage agent-skill lifecycles across local, global, project, Skill Hub, skills.sh, GitHub, plugin-cache, and system roots. Use when searching, recommending, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, or validating skills; choosing project versus global scope; verifying upstream source, stars, or installs; or working with skill-upgrade, check_upstreams.ps1, sync-pull/push, junctions, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Use when first setting up lark-cli, running auth login, switching user/bot identity (--as), handling permission denied or scope errors, needing to update lark-cli, or seeing _notice in JSON output.
日本語の概要は準備中です。原文の説明を表示しています。
Manually run the extended DeepSeek Harness bilingual-document workflow, including generated briefings, delegated prose translation, whole-document translation, and scoped pairing verification.
日本語の概要は準備中です。原文の説明を表示しています。
AI image generation with OpenAI GPT Image 2, Azure OpenAI, Google, OpenRouter, DashScope, Z.AI GLM-Image, MiniMax, Jimeng, Seedream, Replicate and Agnes APIs. Supports text-to-image, reference images, aspect ratios, and batch generation from saved prompt files. Sequential by default; use batch parallel generation when the user already has multiple prompts or wants stable multi-image throughput. Use when user asks to generate, create, or draw images.
日本語の概要は準備中です。原文の説明を表示しています。
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. Use it proactively when an existing skill could be a ready-made building block, while keeping installation scoped to the current project unless the user explicitly requests a global install.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Agent Skills across Codex, Claude Code, local/global/project roots, Skill Hubs, GitHub, skills.sh, and managed plugin caches. Use when searching, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, validating, resolving upstream sources, choosing runtime or scope, or working with skill-upgrade, check_upstreams.ps1, Claude Code plugins, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Define legal scope, rules of engagement, and authorization artifacts for downstream pentest execution.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and orchestrate authorized Nmap host discovery, port and service enumeration, NSE profiling, and reporting artifacts for in-scope targets.
日本語の概要は準備中です。原文の説明を表示しています。
Actively enumerate in-scope hosts and services, then produce normalized network mapping artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Run controlled exploitation against confirmed vulnerabilities while enforcing scope and authorization gates.
日本語の概要は準備中です。原文の説明を表示しています。
Pressure-test startup ideas against real user pain, current behavior, competitors, first-customer access, MVP scope, founder-market fit, and a two-week launch test. Produces a direct strong, weak, or pivot verdict.
日本語の概要は準備中です。原文の説明を表示しています。
GStack guard method for strengthening scope boundaries, forbidden actions, stop conditions, and validation gates for an agent or workstream.
日本語の概要は準備中です。原文の説明を表示しています。