1.1천건 · 관련도순
Turn documents, notes, research, or code into a knowledge graph that maps identifiable things and their relationships. Create or update entity files and typed connections, with source evidence attached for inspection and later visualization.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code changes using a knowledge graph, a map of code relationships, to assess risk and affected behavior. Organize findings by severity, identify missing tests, suggest fixes, and provide a merge recommendation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Polish existing academic PPTX or Beamer slides through page-by-page Codex review against a reference PDF. Adjust typography, spacing, colors, and text overflow while preserving content, keeping the original deck, and recording each change.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Routes requests about a codebase to the appropriate skill for mapping its structure, generating knowledge graphs, updating documentation, extracting lessons, or storing and recalling project knowledge for future planning.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design a dark slide deck for AI products, knowledge graphs, or developer tool launches. Combine a graph-based cover, glowing blurred shapes, gradient section titles, highlighted code or command-line examples, and frosted-glass-style cards.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Distribute edits across the appropriate branches in a Graphite stack, a chain of dependent branches. Use manual grouping when automatic absorption misplaces changes, then update commits, resolve restack conflicts, and verify the affected branches locally.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Select relevant code using Trailmark's map of function relationships, then delegate explanation, review, or edit proposals to a smaller model. Limit the supplied source, check cited evidence, and verify proposed changes before applying them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Query the local AST-derived code graph (functions, classes, calls, imports) for structural codebase questions — what calls X, what does Y import, where is Z defined, blast radius of a change. The graph rebuilds automatically after each agent turn; use hivemind_graph_search and hivemind_graph_neighborhood tools (no manual build step).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decode an OBD-II diagnostic trouble code (DTC) using the CarsXE API. Use this when a user mentions a check engine light code, DTC, or OBD code like P0300, C1234, B0001, or U0100.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; on the default branch it reviews the unpushed and uncommitted work. A bug-hunting code review complements this review and does not replace it. Also use for 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Takes an optional path, tag, topic, or ref in free text; no first word is a mode — say 'are docs out of date', 'audit the knowledge base', 'close out the feature', or 'capture this pattern' in plain words. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use `graphify-dotnet` to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and architecture snapshot generation. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Statically analyze code to detect security vulnerabilities including buffer overflows, injection risks (SQL, command, XSS), insecure deserialization, improper authentication, hard-coded credentials, and unsafe cryptography. Use when: (1) Performing security code review, (2) Analyzing code for OWASP Top 10 vulnerabilities, (3) Identifying CWE-classified weaknesses, (4) Generating security audit reports, (5) Reviewing code before deployment, or (6) Assessing third-party code security. Findings categorized by CWE ID and severity (Critical/High/Medium/Low).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Neo4j Python Driver v6 — driver lifecycle, execute_query, managed and explicit transactions, async (AsyncGraphDatabase), result handling, data type mapping, error handling, UNWIND batching, connection pool tuning, and causal consistency. Use when writing Python code that connects to Neo4j via GraphDatabase.driver, execute_query, execute_read, execute_write, AsyncGraphDatabase, neo4j.Result, or RoutingControl. Package name is `neo4j` (not neo4j-driver) since v6. Python >=3.10 required. Does NOT handle Cypher query authoring — use neo4j-cypher-skill. Does NOT cover driver upgrades or breaking changes — use neo4j-migration-skill. Does NOT cover GraphRAG pipelines (neo4j-graphrag package) — use neo4j-graphrag-skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query patent simple bibliographic (catalog) data from the Nexscope patent database. Triggered when users mention patent bibliographic information queries, patent basic info retrieval, patent catalog data, patent publication details, searching by patent number for inventors, patent applicant information, patent abstract retrieval, patent classification codes (IPC/CPC), patent citation queries, or any request to search for structured metadata by patent ID or publication number, patent brief bibliography, patent basic info, patent number lookup, patent abstract, Nexscope, or patent metadata. Even if the user does not explicitly mention "Nexscope" or "bibliographic info," this skill should be triggered whenever their need involves querying core bibliographic fields of specific patents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unified code intelligence — Skeleton Index (zero-dep, <4s) + AST knowledge graph (CodeGraph) + architecture diagrams (Mermaid) + smart context builder. Pre-indexes code structure so AI agents understand any codebase instantly. 95% token compression for onboarding. 30% fewer tokens for deep analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structural code graph queries via CodeGraphContext MCP (tree-sitter + KuzuDB). Find callers, callees, class hierarchies, dead code, and module dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze codebases using a graph database instead of reading source files. Use when understanding code architecture, finding functions or call patterns, tracing data flow, checking dependencies, or answering "where is X used?" questions. Grafema builds a queryable code graph from static analysis — prefer querying the graph over reading files manually.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for graph-oriented relationships, edge management, and traversal logic on top of Orleans grains. Use when the application models graph structures in a distributed Orleans system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route Microsoft Graph work from VS Code. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode for technical work — a thinking partner for {{engine_name}} code, architecture, and implementation decisions before you write any code. Use it to investigate a technical solution, design the architecture of a feature, choose between frameworks or libraries, compare implementation approaches, analyze how existing code or a system works, or deeply root-cause a complex bug without fixing it yet. The ultra mode adds adaptive artifacts (a C4 view, ADRs, a dependency graph) to the research folder — run it on "ultra research", "ultra explore" or "ultraresearch"; otherwise run the default. Trigger on "let's explore this technical solution", "how should we architect this feature", "which framework should we use", "run an ultra research on the save system", "investigate this error deeply". Research and analysis only — it never writes code. This is the CODE / engineering explorer — for GAME-DESIGN, GDD, mechanics, or balance research (no code) use /unikit-gd-explore.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.