4,066 件 ・ 関連度順
概要と使いどころ
Trace execution time of Python method invocations in a live process with call stack visualization. Use this to see a hierarchical call tree showing which sub-calls are slow and where time is spent within a function.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect live Python class instances in a running process — find all instances of a class, examine their attributes/state, or invoke methods on them. Also supports forcing GC. Use this when you need to probe object-level runtime state beyond what watch/getglobal can provide.
日本語の概要は準備中です。原文の説明を表示しています。
Hot-reload a Python function implementation from the latest file content without restarting the process. Use this to apply code fixes live after identifying a bug with watch/trace.
日本語の概要は準備中です。原文の説明を表示しています。
Prerequisites and connection details for attaching to a live Python process with PyFlightProfiler. Read this skill first before using any other PyFlightProfiler command (watch, trace, stack, perf, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a Wardley Map of how any domain delivers value. Maps the needs it serves, the capabilities involved, how each is evolving (genesis to commodity), and strategic plays. Applies to any domain, not only software.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate a Mycelium project from legacy install (npx-degit, framework files in .claude/) to plugin install (framework lives in plugin cache, .claude/ holds project state only). Detects current install form, walks the user through plugin installation, runs the migration script, and verifies project state survived. Idempotent — safe to invoke on already-migrated projects.
日本語の概要は準備中です。原文の説明を表示しています。
Assess delivery health metrics. For software: DORA + APEX. For content/AI/service products: product-type-appropriate metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Structured retrospective after completing a delivery increment or diamond. Captures learning for continuous improvement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting implementation on a new or unfamiliar codebase. Auto-detects tech stack and sets up development context.
日本語の概要は準備中です。原文の説明を表示しています。
Bring Mycelium into a project that already has code. Detects that the repo predates the framework, asks before touching anything, then reads the codebase to draft what it CAN establish (delivery, solution shape) and — the actual point — names what it cannot (purpose, strategy, real user evidence). The output is a discovery backlog with a head start, never a filled canvas.
日本語の概要は準備中です。原文の説明を表示しています。
Render `.claude/diamonds/active.yml` as the decisions each diamond has recorded, in order, grouped by mode (discovery, delivery). Read-only. Default format Mermaid stateDiagram-v2, drawn by a script. Recommended at the end of `/mycelium:diamond-assess` so every assessment closes with a visual state-of-play. See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared render fleet conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Use before starting delivery work. Pre-implementation validation checklist to ensure readiness.
日本語の概要は準備中です。原文の説明を表示しています。
Maintainer-only. Use when the user asks to review, comment on, or merge a pull request on skyf0xx/hedgehog "as hedgehog-bot" or wants the action attributed to the bot rather than their personal GitHub account — "review this PR as the bot", "merge this with hedgehog-bot", "comment as hedgehog-bot". Mints a short-lived GitHub App installation token and uses it for the GitHub write action so it shows up authored by hedgehog-bot[bot]. Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.
日本語の概要は準備中です。原文の説明を表示しています。
Use for coding, PR delivery, scaffolding and QA. Triggers: develop, fix, refactor, test, review, docs, browse, stacked PR, 개발, 수정, 검토, 스택 PR.
日本語の概要は準備中です。原文の説明を表示しています。
Validates adapter files against live platform documentation to detect stale mappings,missing features, and outdated version information
日本語の概要は準備中です。原文の説明を表示しています。
Use when Codex must make a high-quality judgment on any complex problem, not only technical problems. Trigger when a question has high complexity, uncertainty, cost of being wrong, long-term impact, value tradeoffs, possible structural causes, or when the user asks for 全面思考, 深度理解, 系统性分析, 帮我想清楚, 从根上看, 这件事到底怎么看, 方法论, 复杂问题拆解, 系统方案, 架构判断, 策略判断, or 根因分析. Also trigger for project and engineering high-risk scenarios such as multi-module, multi-environment, multi-data-source, multi-state, financial truth, live trading, ledger, revenue, customer assets, order governance, broker interfaces, online availability, major solution selection, and system closure.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes securities lending market with borrow cost, short interest dynamics, and fail-to-deliver monitoring. Use when analyzing lending markets, tracking borrow costs, or evaluating short selling dynamics.
日本語の概要は準備中です。原文の説明を表示しています。
Refresh evaluation harnesses with live/fallback parser reliability, SLO gates, and regression checks.
日本語の概要は準備中です。原文の説明を表示しています。
Fuzz directories, files, and parameters using ffuf, feroxbuster, arjun, paramspider, and x8. Use when the user has live hosts and needs to find hidden routes, backup files, exposed configs, and untracked URL parameters.
日本語の概要は準備中です。原文の説明を表示しています。
Probe subdomain list with httpx/dnsx/naabu to identify live hosts, open ports, status codes, titles, and basic fingerprints. Use after subdomain-enum produces a sub list. Output feeds into fingerprinting and content discovery.
日本語の概要は準備中です。原文の説明を表示しています。
Extract endpoints, secrets, and hidden routes from JavaScript files using LinkFinder, SecretFinder, JSluice, and source-map analysis. Use when the user has live hosts and needs to mine the JS for attack surface that's not visible in the UI.
日本語の概要は準備中です。原文の説明を表示しています。
Find the most valuable commercial insight and the monetization point closest to lawful revenue for a project, product, service, website, community, content account, open-source tool, or business idea. Use when a user asks how to monetize, who pays, why people do not buy, what to charge, whether to keep building, what to stop, what to do next, or asks to continue or deepen an earlier business analysis. Answer the user's actual question before asking for more information and carry the analysis forward without repeating it. When the buyer, purchased result, or delivery ability is unknown, do not select them from industry stereotypes; use explicit conditional candidates and an evidence-gathering next step. Not for investment advice, income forecasts, get-rich-quick schemes, or guaranteed results.
日本語の概要は準備中です。原文の説明を表示しています。
Declare variables in smallest possible scope, initialize close to first use, minimize span and live time
日本語の概要は準備中です。原文の説明を表示しています。
Plan and freeze workflow execution by creating an Execution Contract, setting PLAN_FROZEN/CURRENT_ROLE, and updating PROJECT_STATE decisions and Top 3. Use when starting workflow delivery, re-planning after unfreeze, or when scope/constraints change before execution.
日本語の概要は準備中です。原文の説明を表示しています。