'code graph' 검색 결과

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build, update, and query a persistent project knowledge graph from skills, memory, docs, and code structure — stdlib Python only, no external tools. Dual-mode: skill-library (agent-loom) or application (any consumer repo). Load when the user asks for a knowledge graph, project map, skill relationships, query the graph, update the graph, or trace how components connect. Auto-runs on memory-handoff and project-setup bootstrap. Also triggers on "build the graph", "what connects to X", "map this project".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

색상·간격·글꼴을 공통 설정으로 정리하고 CSS 변수를 생성합니다. 화면 구성 요소의 상태별 규격과 코드의 직접 지정 값을 확인하며, 같은 브랜드 규칙으로 HTML 발표 자료를 만듭니다.

• 색상·간격·글꼴의 공통 기준 정리
• 버튼의 상태별 규격 정의
• 코드에 직접 지정한 스타일 값 확인

웹 화면 코드를 Vercel 지침에 따라 검토합니다. 배치, 글자, 색상, 움직임, 접근성을 점검하고 문제를 파일명과 줄 번호로 표시하며, 동봉된 고정판으로 검토 기준을 맞춥니다.

• 제품의 화면 코드 검토
• 지침에 따른 사용 편의성 확인
• 배치·글자·색상·움직임 점검

Import Claude Code auto-memory into AgentDB and search past notes by meaning across sessions and projects. The skill checks import status, consolidates near-duplicate entries, and returns search results with their memory sources identified.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Search past notes across projects
• Import all project memories for the first time
• Consolidate near-duplicate memories

Investigate a username, file, code identifier, URL, or concept by exploring connected entities across relevant sources. Produce a dossier with a summary, relationship diagram, source references, and a machine-readable JSON graph.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping connections around a username or concept
• Investigating references to a file or code identifier
• Tracing links to an architecture decision record

Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add integration tests for a new syncable entity
• Test required fields, duplicates, and invalid references
• Verify successful creation, updates, and deletion

Review a repository’s architecture using Ontoly Software Graph, a map of code relationships. Explain module boundaries, package structure, dependencies, and architectural risks, with graph evidence and a stated confidence level.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding a repository’s overall architecture
• Reviewing module boundaries and package structure
• Investigating dependency cycles and architectural risks

Design APIs and interfaces between parts of an application with clear input and output types, consistent errors, and predictable names. The guidance helps you extend existing interfaces while preserving compatibility for the code that uses them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing new REST or GraphQL endpoints
• Defining contracts between frontend and backend
• Reviewing changes to a public interface

Find the right GitNexus tools and workflows for exploring code relationships. This reference explains available commands, graph queries, and resources, including how to check which branch an answer describes and whether its index is current.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find a GitNexus tool for a specific task
• Learn how to query code relationships
• Check index freshness and branch information

Learn how to check Claude Code tool calls against a policy and create digitally signed execution records. This walkthrough covers setup, offline verification, tamper demonstrations, and CI/CD integration before adopting the protect-mcp runtime plugin.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Evaluate signed audit records before adopting runtime hooks
• Demonstrate offline verification and tamper detection
• Verify agent execution records in CI/CD

Create Mermaid diagrams from text to explain software structure, API interactions, workflows, and database relationships. The skill guides diagram selection, syntax, styling, and export, helping keep visual documentation editable and stored alongside code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explaining system architecture with diagrams
• Mapping API requests and responses
• Documenting database table relationships

Guides migration of existing codebases to Rust without unsafe code, covering architecture, implementation, testing, and output comparisons. It measures performance before and after optimization and produces an interactive HTML report documenting results and unresolved differences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Migrating a GitHub or local codebase to Rust
• Comparing original and migrated program outputs
• Measuring and optimizing a Rust port

Audit citations in a LaTeX paper against online sources. Verify that references exist, bibliographic details are accurate, and each cited work supports the surrounding claim, then produce reports with findings and proposed corrections.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking references before paper submission
• Verifying authors, publication years, and venues
• Checking whether cited papers support manuscript claims

Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating an agent failure
• Checking tool selection and execution order
• Investigating memory storage and recall

Inspect imports and agent patterns in existing Python code to identify its framework and recommend an Omnigent executor, the component that runs the agent. Explain unsupported frameworks and suggest available next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identify the framework used by existing Python agent code
• Choose an executor for Claude SDK or OpenAI Agents SDK code
• Check whether a framework has native support

Read frontend source code to document colors, typography, spacing, components, and layout rules in DESIGN.md. Use it to understand an existing interface or prepare design guidance for Stitch without building or running the app.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Document an existing app's design system
• Review styling when the app cannot run
• Prepare an existing visual identity for Stitch

Run Python through the shell when a code sandbox fails to start or connect. Uses a heredoc, a way to pass multiline code, with examples for generating charts, Word documents, and processed JSON files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Continue Python work when the code sandbox is unavailable
• Create a graph image from Excel data
• Generate a Word document with headings and a table

Generates cryptographic test vectors, inputs with expected outcomes, by deliberately changing implementation code and finding changes existing tests miss. Verifies new vectors across independent implementations and compares detection rates before and after adding them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding coverage gaps in cryptographic test vectors
• Creating invalid inputs that exercise validation checks
• Building test vectors shared across independent implementations

Analyze code structure with Trailmark to identify complex functions, trace input flow, assess impact across connected code, and locate privilege boundaries. The resulting JSON provides detailed evidence for deciding where to focus a code audit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing code audit targets
• Tracing input flow and assessing impact
• Inspecting unresolved calls and type references