'dependencies' 검색 결과

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

Configure GitHub Dependabot to keep dependencies, the packages a project relies on, updated. Organize update pull requests into groups, set schedules and exclusion rules, and configure security updates across projects with multiple packages or package systems.

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

• Create or revise dependabot.yml
• Group dependency updates into fewer pull requests
• Configure updates across a monorepo

Explore unfamiliar code with Codebase Memory to map architecture, trace function calls and dependencies, and assess change impact. Findings are checked against source files, with index freshness and coverage considered before drawing conclusions.

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

• Understanding an unfamiliar codebase
• Tracing function callers and dependencies
• Assessing the impact of code changes

Turn feature requirements and technical plans into a structured GitHub project plan. Break work into linked issues, define acceptance criteria, dependencies, priorities, and estimates, and outline board settings and automated progress tracking.

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

• Breaking feature requirements into GitHub Issues
• Mapping dependencies and setting work priorities
• Preparing sprint estimates and completion criteria

Set up a Python project with AWS CDK, a toolkit for defining cloud infrastructure in code. Follow guidance on prerequisites, AWS credentials, virtual environments, dependencies, template generation, deployment preparation, and reviewing changes before deployment.

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

• Setting up a new Python project for AWS CDK
• Preparing a virtual environment and dependencies
• Generating templates and reviewing deployment changes

Analyze Go malware binaries in Ghidra by extracting build metadata, function names, dependencies, and relevant strings. Use GoResolver to help recover obscured names and organize functions so analysts can focus their reverse engineering work.

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

• Investigating the structure of a Go malware sample
• Recovering function names from stripped or obfuscated binaries
• Identifying embedded Go modules and dependencies

Query an indexed code graph, a database of code relationships, to find callers, dependencies, model associations, and call paths. Use the results to understand which components may need attention before changing a function or model.

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

• Find callers before changing a function
• Find serializers affected by model changes
• Trace call paths between functions

Create, modify, test, or package Python provider adapters, the components used for framework connections. Work covers framework dependencies, public imports, type inference, and provider metadata within python/providers, with a referenced workflow to consult before changes.

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

• Create or modify a Python provider adapter
• Adjust framework-specific dependencies and public imports
• Work on type inference and provider metadata

Turn a marketing goal into a campaign brief covering audience, messages, channels, required content, and success measures. Build a weekly content calendar with dependencies, plus budget allocation when provided, risks, and immediate next steps.

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

• Plan a product launch campaign
• Design a lead generation campaign
• Build a weekly content calendar with dependencies

Examine a plan by imagining it has failed twelve months later. Identify weak assumptions, linked dependencies, and commitments that are hard to reverse, then outline validation steps and criteria for continuing, changing direction, or stopping.

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

• Reviewing a plan before committing major resources
• Checking assumptions before a board or investor presentation
• Examining plans that receive only positive feedback

Audit dependency files across eight language ecosystems for built-in vulnerability patterns, license conflicts, and indirect dependency risks. Generate a prioritized upgrade plan with testing and rollback notes, and pair results with live audit tools for current vulnerability coverage.

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

• Auditing third-party packages before a release
• Checking dependencies against built-in CVE patterns
• Reviewing license conflicts across dependency chains

Design and review system architecture, compare databases and structural approaches, and document technical decisions. Included tools generate architecture diagrams, inspect dependencies, and assess project structure to identify circular relationships, excessive coupling, and opportunities for improvement.

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

• Comparing monolith and microservices approaches
• Choosing a database for project requirements
• Generating diagrams from an existing project

Manage shared project tasks in Beads, from finding available work and claiming tasks to tracking dependencies, recording follow-up work, and closing completed items. Keep project status available across sessions and handoffs.

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

• Find tasks that are ready to start
• Claim tasks and record completion
• Track blockers and dependencies

Write a game design document for one system, such as combat, crafting, or dialogue. Work through sections with specialist agent input, check dependencies against existing designs, and save approved sections with progress records for later continuation.

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

• Writing a combat or crafting system design
• Checking dependencies against existing game designs
• Developing specifications with specialist agent input

Review code changes for unnecessary complexity, including unused flexibility, avoidable dependencies, and abstractions with little purpose. Receive concise findings that name what to remove, what can replace it, and how many lines could be cut.

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

• Check code changes for over-engineering
• Find code replaceable with standard library features
• Identify unnecessary dependencies and abstractions

Review source code, dependencies, and infrastructure settings for security issues. Find exposed credentials, unsafe input handling, and access control gaps, then organize findings into a report with severity levels, affected locations, and recommended fixes.

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

• Review code security before deployment
• Find API keys and passwords embedded in files
• Check dependencies for known vulnerabilities

Edit and validate Bazel build settings using conventions specific to CodeQL development. Follow established helpers for packaging and operating system differences, add dependencies with checksums, and check changed targets while respecting the standalone build setup.

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

• Edit CodeQL Bazel build files
• Configure packaging for different operating systems
• Add external build dependencies

Build and test Apache Beam with Gradle, the system that manages its project tasks. Find relevant configuration files, inspect library dependencies, run formatting checks, publish locally, and investigate build failures.

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

• Build or test a specific Apache Beam module
• Inspect library dependencies and version conflicts
• Run formatting and pre-commit checks

Design, review, and implement Gantt charts for project schedules. Assess source data, task dependencies, and resource needs, then define suitable views, editing behavior, rendering tools, accessibility, exports, and tests—or recommend a clearer alternative.

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

• Choose between a Gantt chart, Kanban board, or timeline
• Map project-management exports into schedule data
• Review dependencies, critical path, and baseline variance

Guide code changes in iPolloWork by reusing existing implementations, limiting new files and dependencies, and keeping responsibilities clear. Review runtime costs, run focused checks, and audit the final changes for duplication and maintainability issues.

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

• Checking for reusable code before implementing a feature
• Removing duplicate implementations during refactoring
• Reviewing the need for new files and dependencies

Design and review how a system is divided into modules, cohesive parts with clear responsibilities. Evaluate data ownership, communication rules, dependencies, and failure handling, and decide when to split or merge parts without assuming a particular technology.

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

• Define responsibilities and boundaries for a new module
• Review dependencies between system modules
• Clarify data ownership and communication rules

Analyze dependencies between software modules using connection strength, distance, and frequency of change. Get a dependency map, code evidence, and prioritized recommendations for relationships that make changes spread across the system.

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

• Investigating why changes spread between modules
• Reviewing dependencies between services
• Prioritizing work to reduce coupling

Install PuerTS in a Unity project by selecting a version, identifying required packages and dependencies, and choosing downloads or Git URLs. The guide also covers Editor Assistant installation, verification, and Windows troubleshooting.

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

• Install PuerTS packages in a Unity project
• Set up the PuerTS Editor Assistant
• Identify dependencies for agent or mcp

Audit and update Pilot Shell upstream dependencies in installer/upstreams.yaml. Checks npm, PyPI, brew, and curl-pipe entries for newer stable versions, known security advisories, and sha256 drift. Verifies each update installs successfully before committing. Use when: "check upstreams", "update dependencies", "audit upstreams.yaml", "are our dependencies up to date", "supply chain check".

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