'dependency graph' 검색 결과

Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).

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

Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".

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

Establish MSBuild/.NET build performance baselines before optimizing. USE FOR: unranked slow builds; cold, warm, incremental or no-op measurements; before/after comparisons; CI output caching; static graph, artifacts output and dependency graph trimming. Start here before build-perf-diagnostics, incremental-build or build-parallelism. DO NOT USE FOR: known repeated-restore fixes (use eliminate-redundant-restores), non-MSBuild builds. For measured target/task/analyzer bottlenecks, use build-perf-diagnostics.

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

Generate Mermaid architecture diagrams from your codebase. Produces C4 context and container diagrams, sequence diagrams for key flows, ER diagrams from database schemas, and module dependency graphs. Use when you need architecture diagrams, system diagrams, database ERD, sequence diagrams, dependency visualization, or C4 model diagrams.

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

Expert guide for in-memory Abstract Syntax Tree (AST) code knowledge graphs, real-time symbol dependency mapping, refactoring blast radius calculation, and dead code eradication / Panduan ahli graf pengetahuan AST kode in-memory, pemetaan dependensi simbol real-time, kalkulasi radius dampak refaktor, dan pembersihan kode mati.

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

Fix missing theorem proof terms when analyzing Lean 4 environments via importModules. Use when: (1) ConstantInfo.value? returns none for theorems despite TheoremVal.value being Expr, (2) building code graph / dependency extractor for Lean 4 and getting 0 proof dependency edges, (3) Lean 4.30+ project where theorem proofs appear missing from loaded environment, (4) analyzing Mathlib or any Lean 4 project and proof terms are empty. Root cause: breaking change in Lean 4.30 — value? treats theorems as opaque by default.

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

Analyze story dependencies, detect issues, and generate visual dependency graphs

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

Generate Mermaid architecture diagrams from your codebase. Produces C4 context and container diagrams, sequence diagrams for key flows, ER diagrams from database schemas, and module dependency graphs. Use when you need architecture diagrams, system diagrams, database ERD, sequence diagrams, dependency visualization, or C4 model diagrams.

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

Establish build performance baselines and apply systematic optimization techniques. Only activate in MSBuild/.NET build context. USE FOR: diagnosing slow builds, establishing before/after measurements (cold, warm, no-op scenarios), applying optimization strategies like MSBuild Server, static graph builds, artifacts output, and dependency graph trimming. Start here before diving into build-perf-diagnostics, incremental-build, or build-parallelism. DO NOT USE FOR: non-MSBuild build systems, detailed bottleneck analysis (use build-perf-diagnostics after baselining).

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

GitHub 公式ドキュメント (docs.github.com)。REST API, GraphQL, Webhooks, GitHub Apps, OAuth Apps, gh CLI, PAT / GITHUB_TOKEN, Actions (jobs, steps, expressions, workflow commands, concurrency, OIDC, artifact attestations, lockfile), pull requests, issues, Projects v2, immutable releases, Codespaces, Packages, Copilot API / cloud agent, code scanning, secret scanning, Dependabot, Dependency graph / SBOM, Teams, Billing, activity (events / notifications)。

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

Organize a task into parallel work streams with clear dependencies, separate places for changes, and explicit checks. Batch independent reads and tests, coordinate concurrent work, and report completed or blocked tasks with verification results.

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

• Batching independent file reads and searches
• Splitting implementation across multiple agents
• Separating changes with Git worktrees

대규모 기능 개발이나 마이그레이션 목표를 여러 차례 수행할 실행 계획으로 나눕니다. 단계별 배경, 의존 관계, 검증 방법을 정리해 다른 에이전트에게 작업을 인계할 수 있게 합니다.

• 대규모 기능을 여러 PR로 나눕니다
• 여러 세션에 걸친 마이그레이션을 계획합니다
• 병렬로 진행할 수 있는 단계를 찾습니다

여러 Orca 작업자에게 일을 나누고 진행을 감독합니다. 메시지 교환, 완료 보고와 판단 요청 대기, 작업 의존 관계 관리를 통해 에이전트 간 협업을 조율합니다.

• 여러 Orca 작업자에게 작업 분배
• 의존 관계가 있는 작업의 진행 관리
• 작업 완료 보고나 판단 요청 대기

Organize complex work for a team of AI agents by splitting tasks, defining dependencies, and documenting ownership and completion criteria. Provides strategies for tracking progress, spotting blockers, and redistributing work when workloads become uneven.

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

• Splitting complex work among multiple AI agents
• Mapping dependencies and execution order
• Defining file ownership and acceptance criteria

Create and update GitHub issues for bugs, feature requests, and tasks. Organize owners, labels, dates, and priorities, connect related work, and track dependencies and project progress through MCP tools and the GitHub API.

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

• File bug reports and feature requests
• Update issue owners, dates, and priorities
• Organize parent tasks, subtasks, and dependencies

Review code changes against the previous commit and identify affected files and functions. Use dependency relationships to assess risk, check missing tests, and produce a focused report with issues and recommendations.

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

• Reviewing changes against the previous commit
• Checking how a change affects other functions
• Finding missing tests for high-risk changes

Build PHP 8.3+ applications with Laravel or Symfony, including typed models, services, APIs, and tests. Use static analysis, which checks code without running it, alongside automated tests to verify the implementation.

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

• Building APIs with Laravel or Symfony
• Separating business logic from controllers
• Creating typed data objects and domain models

Create editable FigJam diagrams for workflows, system architecture, data relationships, and schedules. The skill selects a suitable diagram type and guides Mermaid, a text format for diagrams, while accounting for rendering limits.

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

• Visualizing a workflow or decision tree
• Mapping services and data stores
• Showing API interactions over time

Choose, create, and review software diagrams that explain structure, interactions, workflows, states, or data relationships. Select suitable notation and rendering tools, then plan static exports or interactive views with readable layouts, accessible controls, and validation.

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

• Explain login interactions with a sequence diagram
• Turn a database schema into an entity relationship diagram
• Document application architecture with C4

Create editable FigJam diagrams for workflows, system architecture, data relationships, and schedules. The skill selects a suitable diagram type and guides Mermaid, a text format for diagrams, while accounting for rendering limits.

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

• Visualizing a workflow or decision tree
• Mapping services and data stores
• Showing API interactions over time

Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes. Use for architecture orientation, impact analysis, what-would-break questions, or finding callers. Uses CodeGraph when available and a dependency-free builtin fallback.

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

Compile-time dependency injection in Golang using google/wire — wire.NewSet, wire.Build, wire.Bind (interface→concrete), wire.Struct, wire.Value, wire.InterfaceValue, wire.FieldsOf, cleanup functions, //go:build wireinject injector files, and generated wire_gen.go. Apply when using or adopting google/wire, when the codebase imports `github.com/google/wire`, or when wiring an application graph at compile time via `wire.Build`. For runtime DI with reflection, see `samber/cc-skills-golang@golang-uber-dig` skill.

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

Implements dependency injection in Golang using uber-go/dig — reflection-based container, Provide/Invoke, dig.In/dig.Out parameter and result objects, named values, value groups, optional dependencies, scopes, and Decorate. Apply when using or adopting uber-go/dig, when the codebase imports `go.uber.org/dig`, or when wiring an application graph at startup. For higher-level lifecycle and modules, see `samber/cc-skills-golang@golang-uber-fx` skill.

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

Create text-driven visuals in Markdown: charts, diagrams, cards, architecture and page layouts. Charts and analytical views (bar, line, pie, heatmap, correlation, regression); reliability and operations (latency, incident, throughput, cycle time, OKR, standup, on-call); product and finance (funnel, retention, revenue, budget); process and workflow (approval, BPMN); software design and behaviour (class, state machine, sequence, C4); dependencies and impact (dependency graph, ER, causality); system architecture as HTML (layer stack, wings, zones, topology, service catalogue, request paths); infrastructure (cloud, Kubernetes, ETL, network, security, IAM, compliance); governance and people (ArchiMate, org chart, hiring); knowledge and planning (mind map, roadmap, Gantt, migration); documents (comparison, SWOT, memo, policy, catalogue, case study). Use when a document needs a diagram, chart or card. Figures render live. Not for slide decks or math notation. Not recommended: mermaid / canvas / drawio / dot.

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