'code analysis' 검색 결과

Generate a customizable AI prompt for finding representative examples in an existing codebase. Configure analysis depth, categories, and snippets so GitHub Copilot can produce exemplars.md with real file references and explanations of coding conventions.

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

• Collecting existing code examples for team guidance
• Documenting patterns to follow when adding features
• Configuring the depth and format of a code example guide

Learn Claude Code workflows through a Chinese-language guide covering tool use, large-file analysis, task tracking, and troubleshooting. It also explains MCP, a protocol for connecting external systems, alongside development and review patterns.

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

• Learn tool use and development workflows
• Analyze large files in manageable sections
• Study MCP connections to external systems

Structure and revise investment research into readable Markdown reports for Codex. Explain business economics, competitive advantages, opposing arguments, and valuation, then connect the evidence to price bands and actions for prospective investors and existing holders.

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

• Restructure a lengthy investment research report
• Explain how a company earns money and sustains its advantages
• Strengthen a report's bear case and observable risk indicators

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

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

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams

Turn existing source code into reusable learning materials. This skill identifies architectural patterns and implementation techniques, then organizes them into a SKILL.md with structured metadata, explanatory code templates, practical examples, and validation steps.

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

• Create teaching materials from reference code
• Document reusable implementation patterns
• Prepare code templates with usage examples

Get a quick structural overview of a codebase with Trailmark. The skill identifies programming languages, counts entry points where execution begins, and returns dependency information to support orientation before deeper analysis.

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

• Getting oriented in an unfamiliar codebase
• Checking languages and entry point counts before analysis
• Preparing a structural overview for Vivisect or Galvanize

Reviews code changes for security risks using Git history, caller counts, and test coverage. Produces a Markdown report with evidence, potential attack scenarios, affected code, and clear limits on what was reviewed.

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

• Reviewing a pull request for security risks
• Checking whether a fixed bug has returned
• Assessing which callers a change could affect

Scan source code for security weaknesses with Semgrep after approving the target and rulesets. Choose full results or focus on important findings, then receive merged results and a record of failed or skipped scans.

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

• Audit source code for security weaknesses
• Check for vulnerabilities before code review
• Focus on findings with medium-to-high confidence and impact

Analyze business concepts in a codebase to map business areas and suggest service boundaries. Use Domain-Driven Design, an approach organized around business meaning, to classify responsibilities, assess how closely they belong together, and recommend clearer integration points.

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

• Mapping business capabilities in an unfamiliar codebase
• Planning service boundaries around business terminology
• Reviewing mixed responsibilities before refactoring

Organize existing code components into business areas to prepare for service separation. Produce domain maps, component assignment tables, and refactoring plans that align namespaces, the naming structure used to organize code, with business responsibilities.

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

• Grouping existing components by business responsibility
• Planning service extraction from an existing application
• Aligning code namespaces with business areas

Explore code through structured summaries of functions, calls, branches, and variable usage. Use the tldr commands to locate relevant files, trace change impacts, find affected tests, and identify potentially unused code before inspecting the implementation.

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

• Understanding an unfamiliar codebase
• Tracing callers and the impact of a change
• Investigating bugs across multiple files

Read-only R code review protocol for `.R` scripts. Checks code quality, reproducibility, domain correctness, tidyverse idioms, and professional standards; produces a report without editing. Use when user says "review this R script", "check the R code", "audit the analysis code", "code review on the R", or when an R file is touched as part of a paper submission. NOT for running the code — pair with `/audit-reproducibility` for numeric verification.

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

Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing

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

Measures cyclomatic complexity, cognitive complexity, and function length across codebases to identify maintenance hotspots. Use when someone asks about code complexity, function length analysis, maintainability metrics, or needs to find the most complex parts of their codebase. Trigger words: complexity, cyclomatic, cognitive complexity, long functions, hotspots, maintainability index, code metrics.

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

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

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

Interactive codebase orientation for a HUMAN who wants to learn the code. Runs the same tree-sitting + featuring pipeline as exploring-codebases but synthesizes it into guided exercises and an HTML teaching artifact rather than an analysis document. Use for "orient me to this repo", "teach me this codebase", "walk me through this code", "learning orientation", or when someone wants genuine comprehension rather than a task completed. The audience is the test: if nobody is being taught and the goal is to get work done, use exploring-codebases instead.

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

Run CodeQL static analysis for security vulnerability detection, taint tracking, and data flow analysis. Use when asked to analyze code with CodeQL, create CodeQL databases, write custom QL queries, perform security audits, or set up CodeQL in CI/CD pipelines.

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

Emulates position-independent shellcode in a controlled CPU emulator (Unicorn) to trace executed instructions, memory writes, and decoded second stages without running it on a real host. Activates for requests to emulate shellcode, trace a decoder stub, or recover a stage unpacked at runtime by shellcode.

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

코드의 결함, 취약점, 성능, 유지보수성과 테스트를 점검합니다. 문제의 위치와 영향, 수정안, 개선점과 장점, 병합 가능 여부를 정리한 리뷰를 작성합니다.

• 병합 전에 변경 사항을 리뷰합니다
• 결함과 경계 조건을 확인합니다
• 취약점과 의존성을 점검합니다

Claude Code 세션에서 지정한 시각이나 간격으로 감사, 테스트 커버리지 분석 등을 실행할 워커를 등록하고 정기 작업을 확인하거나 해제합니다.

• 15분마다 보안 검사를 실행합니다
• 테스트 커버리지를 정기 확인합니다
• 두 시간마다 API 문서를 생성합니다

Review source code with Strix to trace data flow and authorization checks, then test suspected vulnerabilities in a running environment. Receive proven findings with exploit examples and code locations, while keeping unconfirmed observations clearly identified.

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

• Reviewing a repository for security vulnerabilities
• Checking authorization logic in a specific service
• Reviewing security risks introduced by a branch

Review GitHub Actions workflows that run AI agents, tracing how external input reaches prompts and tools. Produce findings with evidence, severity, impact, and remediation guidance through static analysis, which examines configuration without running attacks.

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

• Auditing AI agent integrations in GitHub Actions
• Tracing issue and PR text into agent prompts
• Reviewing sandbox settings and tool permissions

Understand and extend GitNexus taint analysis, which tracks data from input sources to potentially dangerous operations. Use its implementation guidance to investigate missed or incorrect findings, add detection models, and validate analysis changes.

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

• Investigating missed or incorrect data-flow findings
• Adding input sources, dangerous operations, or sanitizers
• Reviewing analysis that follows data across functions

Analyze compiled programs without running them by recognizing branches, loops, data structures, and common instruction patterns. Use disassembly and decompilation, which translate machine code into readable representations, to reconstruct program logic and document findings.

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

• Understand an unfamiliar executable
• Reconstruct branches and loops from assembly
• Infer data structures and function parameters