97건 · 관련도순
Build a graph of functions and calls across multiple programming languages to investigate entry points, paths to sensitive operations, and potential impact. Use the results to prioritize security reviews and connect external findings with source code.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create Mermaid diagrams from code relationships parsed by Trailmark. Visualize function calls, class inheritance, module dependencies, class members, complexity hotspots, and paths from inputs to sensitive functions, with adjustable focus, depth, and layout.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze git history to map contributors to security-sensitive files and identify ownership gaps. Estimate bus factor, a measure of dependence on few people, group files that change together, and export CSV or JSON for further analysis.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate observed slowdowns or increased CPU, memory allocation, and IO costs in a process you control. Use controlled timing and runtime-specific profiling tools to test a cause, then check performance and behavior after a fix.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] Software slowness, memory leaks, or cost spikes: find where a system is actually slow, leaking, or expensive across runtime, memory, token cost, storage, rendering, inference, CI, and query domains, then fix one measured hot path at a time behind a regression budget. Use when the user says: ultraperf, ulw-perf, performance audit, performance bottleneck, find the bottleneck, profile the hot path, memory leak investigation, token cost hotspot.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve conflicts and merges when several branches are open against one repo at the same time — the hotspot files every change must touch (registry manifests, a single version field, shared tool config, one aggregated test module, tracked build output), union-vs-recompute-vs-rebuild as three different correct resolutions, generated artifacts that must never be merged, non-deterministic serialization that makes every branch conflict, renumbered identifiers that git cannot show you, and why a clean auto-merge is not a passing test. Use when rebasing or merging a long-lived branch, resolving conflict markers, reviewing a merge commit, deciding what a repo should commit vs generate, or setting up a repo that will take parallel contributions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
小红书热点搜集与选题判断。按关键词/赛道拉取近期高互动笔记，输出热点表格、趋势判断和可直接开写的选题建议。当用户说"小红书热点""小红书最近火什么""查一下 XX 赛道的爆款""小红书选题""找小红书素材""这个词在小红书热不热""小红书热榜/热门笔记/爆款笔记""帮我看看小红书数据"时触发。也适用于用户报出一个赛道词（如"减脂餐""通勤穿搭""AI 工具"）并问"能不能写"的场景。多数据源自动降级：红狐 API / socialdatax CLI / 怪壳 CLI，均未配置时走 WebSearch 手动兜底。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
First-time Archcore setup. Wires the host (MCP config, hooks, CLAUDE.md/AGENTS.md managed block), measures the authored context the repo already holds, then composes a first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm. Modes, named as the first word: init import converts the repo's authored context — CLAUDE.md, AGENTS.md, .cursor/rules and other agent instructions, ADR and RFC folders, contributor docs, internal pages of a published docs site, recoverable git history — into native typed documents with no import marks, staged by a plan when the volume is large; init refresh adds facts that appeared since, or drills into one domain with init refresh <domain>. Use on a fresh clone, empty `.archcore/`, 'set up archcore', 'migrate our CLAUDE.md to archcore', 'import our docs and ADRs', or to wire host configs. Not for individual docs or planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code. Use OpenCover format with ReportGenerator for Risk Hotspots showing cyclomatic complexity and untested code paths.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plot per-gene mutation distributions on a protein-domain map (lollipop / needle plots) showing mutation position, recurrence count, and variant classification with maftools, g3-lollipop, trackViewer, and ProteinPaint. Use when visualizing recurrent mutation hotspots on a single gene's protein, marking domain boundaries from UniProt/Pfam, comparing missense vs truncating distributions, or contrasting two cohorts on the same lollipop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Data-driven sprint retrospectives from git history — velocity, cycle/lead time, contributor insights, and churn hotspots. Use to run a retrospective, analyze team velocity or throughput, or generate a retro report from commit history.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze a software codebase for algorithmic complexity and performance hotspots, then propose or implement safe optimizations without breaking behavior. Use when Codex is asked to scan many files, find inefficient loops, nested iteration, repeated scans, costly rendering/recomputation, N+1 queries, avoidable O(n^2) or O(n) operations, or reduce complexity such as O(n^2) to O(n log n) / O(n), while preserving tests, APIs, outputs, and maintainability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when using the Popochiu addon — point-and-click adventure framework with rooms, characters, props/hotspots, inventory, dialog trees, and a command-based GUI
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use dotnet-diagnostics-mcp for MCP-driven .NET CPU, allocation, GC, and test-host profiling. USE FOR: profiling unit tests or investigating runtime bottlenecks. DO NOT USE FOR: writing test assertions, coverage collection, or precise microbenchmark timing. INVOKES: connect the MCP server, select target processes, collect bounded profiles, and attribute hotspots to source.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. This should trigger for requests such as Analyze JFR profile; Analyze the profile; Analyze the performance; Analyze the memory; Analyze the threading; Analyze GC logs from profiling; Prioritize Java profiling bottlenecks by impact. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects time and space complexity hotspots via AST scan. Use when code feels slow, before performance-sensitive merges, or to find O(n²) regressions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Native macOS/iOS app performance profiling via xctrace/Time Profiler and CLI-only analysis of Instruments traces. Use when asked to profile, attach, record, or analyze Instruments .trace files, find hotspots, or optimize native app performance without opening Instruments UI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forensic root cause analyzer for Antigravity sessions. Classifies scope deltas, rework patterns, root causes, hotspots, and auto-improves prompts/health.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect and analyze areas with high maintenance cost, poor design, or accumulated technical debt. Use this skill when reviewing codebases for quality issues, planning refactoring efforts, conducting code audits, assessing project health, identifying maintenance hotspots, or prioritizing technical improvements. Analyzes code smells, architectural issues, dependency problems, test quality, documentation gaps, and provides actionable recommendations with priority rankings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Profile programs at the function/method level to identify performance hotspots, bottlenecks, and optimization opportunities. Records execution time, memory usage, and call frequency for each interval. Generates actionable recommendations and visualizations. Use when users need to (1) analyze program performance, (2) identify slow functions or bottlenecks, (3) optimize execution time or memory usage, (4) profile Python, Java, or C/C++ programs with test cases or workload scenarios, or (5) generate performance reports with flame graphs and recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.