Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
日本語の概要は準備中です。原文の説明を表示しています。
1,481 件 ・ 関連度順
概要と使いどころ
Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to ask questions about a codebase or understand code using a knowledge graph
日本語の概要は準備中です。原文の説明を表示しています。
Extract business domain knowledge from a codebase and generate an interactive domain flow graph. Works standalone (lightweight scan) or derives from an existing /understand knowledge graph.
日本語の概要は準備中です。原文の説明を表示しています。
Launch the interactive web dashboard to visualize a codebase's knowledge graph
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.
日本語の概要は準備中です。原文の説明を表示しています。
Perform thorough code reviews with security, performance, and maintainability analysis. Use when user asks to review code, check for bugs, or audit a codebase.
日本語の概要は準備中です。原文の説明を表示しています。
External agent skill (MIT, github.com/DietrichGebert/ponytail). Forces the laziest solution that actually works: question whether the task needs to exist at all (YAGNI), reuse what is already in the codebase, reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Climb the ladder on every coding task — writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Supports intensity levels: lite, full (default), ultra. Never cut validation, error handling, security, or accessibility.
日本語の概要は準備中です。原文の説明を表示しています。
Run full security scans on the codebase using Ruflo security tools. Use when reviewing PRs for security regressions, auditing auth/input-handling code, before production deploys, or when the user asks for a security check at quick/standard/deep depth.
日本語の概要は準備中です。原文の説明を表示しています。
Validate domain boundaries -- detect cross-context import violations and aggregate invariant issues. Use when auditing a DDD codebase for leaks between bounded contexts, before merging cross-cutting changes, or as a CI gate to catch boundary erosion early.
日本語の概要は準備中です。原文の説明を表示しています。
Build a graph-structured dossier on a seed entity via parallel fan-out + recursive expansion across web, memory, knowledge-graph, codebase, ADR index, and git intel
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
日本語の概要は準備中です。原文の説明を表示しています。
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing TypeScript files for type safety regressions, during code review of functions that handle external data, or when the codebase has ESLint warnings for @typescript-eslint/no-explicit-any.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing a site's internal and external links for protocol consistency, migrating a site from HTTP to HTTPS, or reviewing hardcoded URLs in a codebase that may use `http://` instead of `https://`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing or improving any frontend codebase against the full Front-End Checklist rule corpus through one entry point.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing a CSS architecture for specificity issues, setting up a design system, or migrating a large codebase from utility-first to a layered architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Benchmark CodeGraph retrieval quality on a real codebase by comparing agent behavior with vs without CodeGraph. Use when the user runs /agent-eval or asks to test, benchmark, audit, or validate a codegraph version (the local dev build or a published npm version) against a language's repo.
日本語の概要は準備中です。原文の説明を表示しています。
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work. Also use when the user says "openspec onboard" or "opsx onboard".
日本語の概要は準備中です。原文の説明を表示しています。
ACTIVATES ONLY on an explicit user request for the ulw-plan workflow: the user themselves saying ulw-plan, ulw plan, /skill:ulw-plan, or asking in their own words for a work plan before coding. NEVER self-activates: a bare ulw/ultrawork run, an agent-side routing decision, or reading this file is not a request, and the plan-gated reviewers (metis/momus) stay locked without a user request plus a written .omo/plans plan file. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker executes with zero further interview. Triggers: ulw-plan, ulw plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode.
日本語の概要は準備中です。原文の説明を表示しています。
Team Mode security research skill. Orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity by actual exploitability. Use for security review, vulnerability research, exploitability audit, pre-release security check, threat model validation, and `/security-research`. Triggers: 'security-research', 'security research', 'security review', 'vulnerability audit', 'exploitability audit', '보안 리뷰', '취약점 감사'.
日本語の概要は準備中です。原文の説明を表示しています。
Health-check the user's Claude Code setup and fix issues: diagnose installation health — what the `claude doctor` terminal diagnostics cover — from local data (duplicate or leftover installs, PATH, unparseable settings files, broken or colliding agent definitions, skills whose frontmatter fails to parse); find unused skills, MCP servers, and plugins versus their context cost and disable dead weight; deduplicate local CLAUDE.md files against checked-in ones; trim checked-in CLAUDE.md files by cutting content a session could derive from the codebase (directory layouts, tech-stack lists, architecture overviews) while keeping gotchas, rationale, and non-standard conventions; migrate always-loaded CLAUDE.md guidance into lazy skills and nested CLAUDE.md files; flag slow hooks and context-heavy extensions; check the installed version is current; make auto mode the default permission mode; and pre-approve frequently denied read-only commands. Use when the user asks for a doctor run, checkup, audit, tune-up, or cleanup of their Claude Code setup or configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize a new CLAUDE.md file with codebase documentation
日本語の概要は準備中です。原文の説明を表示しています。
Initialize new CLAUDE.md file(s) and optional skills/hooks with codebase documentation
日本語の概要は準備中です。原文の説明を表示しています。