'code analysis' 검색 결과

Review FastGPT pull requests or local branch changes by examining actual code differences. Explain behavior changes and affected areas, identify unrelated changes, and report concrete concerns about code quality, consistency with nearby implementations, and missing test coverage.

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

• Understanding the behavior changes in a FastGPT pull request
• Comparing a local branch with upstream/main
• Identifying unrelated changes or excessive refactoring

Reviews recent Codex conversations to identify coding habits, strengths, and recurring challenges. Produces a prioritized growth report with practical next steps and relevant HackerNews reading, then delivers it to your Slack direct messages.

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

• Reviewing recent coding habits
• Identifying recurring technical challenges
• Choosing learning topics from actual work

Review medium to large code changes using checks selected for the actual patch. Analyze the change and surrounding code, assign focused reviews by function, file, or feature, and combine findings with locations, confidence levels, and supporting evidence.

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

• Reviewing patches of roughly 50 to 1,000 lines
• Checking risks specific to a changed feature
• Reviewing changes alongside callers and related implementations

Uses a known or suspected vulnerability to find related code through Trailmark's graph of calls, types, and implementations. Produces ranked review targets with reasons and limitations for follow-up security analysis.

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

• Finding variants of a known vulnerability
• Prioritizing code that shares sensitive operations
• Preparing candidates for Semgrep or CodeQL review

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

Build isolated code execution environments on Cloudflare Workers for AI-generated code, scripts, and build pipelines. Covers running commands, managing files, preserving interpreter state, exposing service previews, and cleaning up sandbox resources.

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

• Build an execution environment for AI-generated code
• Run build and test pipelines in isolation
• Preview a web service running in a sandbox

Analyze datasets in R or Python, from exploring distributions and missing values to fitting regressions. Produce tables and figures for publication, save scripts and model results, and review the analysis for common problems.

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

• Explore distributions, missing values, and relationships
• Run regressions on cross-sectional or panel data
• Export publication-ready regression tables and figures

Scan projects for known dependency vulnerabilities, exposed credentials, and risky code patterns such as SQL injection. Produces text or JSON reports with file locations and severity levels, with options to run individual checks.

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

• Checking dependency vulnerabilities before release
• Finding hardcoded API keys and passwords
• Reviewing code for common security weaknesses

Create background workers that analyze code, detect exposed secrets, learn code patterns, or generate API documentation. Combine predefined processing stages or start from presets, configure target files in YAML, and inspect worker status and analysis results.

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

• Scan authentication code for security issues and exposed secrets
• Generate API documentation from endpoints and types
• Analyze code complexity and dependencies

Find unused functions through static analysis, which examines code without running it. Scan a project or directory, choose a language, and exclude designated entry points to get a list of functions with file locations.

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

• Listing unused functions across a project
• Checking a specific directory before cleanup
• Excluding entry points and handlers from analysis

Review code that has not yet been checked by forming security hypotheses and testing them with analysis tools. The skill records evidence, checks whether affected code is reachable, searches for related patterns, and preserves review progress across sessions.

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

• Reviewing code that has not yet received security checks
• Testing suspected vulnerabilities with analysis tools
• Searching the codebase for patterns behind confirmed findings

Review generated or changed production code before it ships, using Clean Code, SOLID, DRY, KISS, YAGNI, and LLM-specific failure-mode checks in any programming language. Best used reactively after an agent writes, edits, refactors, or fixes code, before presenting, committing, or merging the result. Use when the user asks "review this PR", "is this safe to merge?", "make this cleaner", "audit this code", "refactor this", "fix this bug", or after a coding agent produced implementation code. Can also guide writing when explicitly invoked before a risky edit. Invoke it on your own initiative the moment you finish writing, editing, or refactoring non-trivial production code, before presenting or committing — don't wait to be asked. DO NOT USE for factual/conceptual questions, CI/tooling config, git workflow, running/debugging tests, pure architecture discussion, prose writing, data analysis, or test-code review (use test-guard).

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

Scans a Power Pages site project for security issues in source code and dependencies. Runs static analysis and dependency scanning, then surfaces findings by category (code patterns, vulnerable packages, secrets, license issues). Use when the user wants to review code for security problems, check for vulnerable packages, find hard-coded secrets, run a code scan, or asks "is my code safe?", "check my dependencies", "find security issues in my source" — even if they say "audit my code" without mentioning specific tools.

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

The package CellBarcode performs Cellular DNA Barcode analysis. It can handle all kinds of DNA barcodes, as long as the barcode is within a single sequencing read and has a pattern that can be matched by a regular expression. \code{CellBarcode} can handle barcodes with flexible lengths, with or without UMI (unique molecular identifier). This tool also can be used for pre-processing some amplicon data such as CRISPR gRNA screening, immune repertoire sequencing, and metagenome data.

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

Run a comprehensive code review on local source files. Use this skill when the user asks to review, audit, inspect, evaluate, or check code, even if they never use the word "review." Does not post comments to GitHub pull requests — use post-code-review-to-pr for that. Does not analyze architectural structure or module boundaries — use architectural-analysis for that. Does not explain code or a PR to build understanding before reviewing — use code-overview for a written overview, or code-walkthrough to be paced through it one step at a time. Does not map bounded contexts or domain boundaries — use ddd-analysis for that. Does not capture feedback on Han's own skills — use han-feedback for that.

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

Analyzes an existing codebase using strategic Domain-Driven Design to discover bounded contexts, surface ubiquitous language and semantic collisions, find places where code boundaries diverge from domain boundaries, and produce an evidence-backed domain and context map. Use when the goal is DDD-specific: bounded context discovery, ubiquitous language analysis, domain model discovery, or mapping contested ownership and responsibility. The entire repository is a valid scope; no module or directory must be named first. Does not assess architectural coupling, cohesion, or technical debt — use architectural-analysis. Does not design service communication, integration patterns, or deployment topology — use architectural-analysis or plan-a-feature. Does not refactor code, diagnose bugs, or review code quality — use refactor, investigate, or code-review.

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

This skill provides systematic bug detection and discovery capabilities for VS Code extensions. Use when searching for hidden bugs, analyzing code for potential issues, investigating suspicious behavior, performing code audits, or proactively finding bugs before they manifest. Covers static analysis patterns, dynamic analysis techniques, code smell detection, and systematic codebase investigation.

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

Carves injected PE images and position-independent shellcode from a memory dump or carved region, identifies the payload type, and prepares it for disassembly or emulation. Activates for requests to recover injected code, carve shellcode from memory, or reconstruct a dumped payload for analysis.

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

Access ENCODE uniform analysis pipelines, generate user-specific Nextflow/WDL pipelines, manage compute resources, and integrate with cloud platforms. Use when the user wants to understand ENCODE pipelines, run pipelines on their own data, generate custom Nextflow workflows from ENCODE pipeline code, check compute requirements (CPU/GPU/memory), run pipelines in background, or integrate with Google Cloud, AWS, or other cloud platforms. Also use when the user asks about ENCODE pipeline outputs, processing standards, software versions, or wants to replicate ENCODE processing. Covers local execution, HPC, and cloud deployment with resource-aware scheduling. Use this skill for ANY pipeline execution, workflow generation, or compute resource management task involving ENCODE data.

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

Iteratively detects and auto-fixes technical debt in a codebase using three quality criteria from debt-analysis references: conditional branch simplification, encapsulation, and separation of concerns. Applies fixes directly to code, runs existing tests to verify no regressions, re-analyzes, and loops until all high-severity issues are resolved or max iterations (5) reached. Use this skill when you want to automatically improve code quality with real code changes, reduce technical debt systematically, or clean up code to meet quality standards. Trigger on phrases like "fix technical debt", "clean up code quality", "refactor and fix issues", "improve code quality automatically", "apply debt fixes", "fix code problems", "eliminate debt".

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

Analyze any codebase's source code in depth and produce structured analysis documents saved as markdown files. Use this skill whenever the user asks to understand how a codebase works — architecture, module design, call flows, data models, design patterns, performance characteristics, or any implementation detail. Trigger on phrases like "analyze the source", "explain this code", "how does X work", "where is Y implemented", "trace the flow of", "what happens when", "read through the code", "code walkthrough", "源码分析", "代码解读", "实现原理", "架构分析", "调用链路", "模块分析", or any code-exploration request. Works with any programming language: TypeScript/JavaScript, Java, Python, Go, Rust, C/C++, and more. Even if the user's question seems simple (e.g., "这个文件是干什么的"), use this skill — a thorough, source-backed analysis document is always more valuable than a surface-level guess.

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

ruflo 분석 명령으로 코드 변경 위험과 복잡한 부분을 확인하고 파일 통계를 살펴봅니다. 이미 수정한 버그의 재발을 막는 CI 점검 실행과 추가도 지원합니다.

• 코드 변경 위험 확인
• 복잡한 코드 찾기
• ruflo 회귀 점검 실행

Route authorized reverse engineering, security analysis, CTF challenge, and defensive testing requests to specialist skills in a local repository. This Codex adapter selects the relevant workflow and checks the task scope before target actions begin.

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

• Selecting a specialist skill for reverse engineering
• Starting security analysis with a defined scope
• Routing CTF challenge tasks to a suitable workflow

Review authorized source code or pull request changes for security flaws. Combine automated static analysis, which checks code without running it, with manual validation to document affected locations, data flows, reproduction examples, and suggested fixes.

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

• Reviewing pull request changes for security issues
• Checking scanner findings for false positives
• Investigating authorization and injection flaws