'dependency' 검색 결과

Run the "get dependencies current" flow for this monorepo — sweep for available updates, triage into safe / deliberate / wait buckets, bump the pnpm catalog, and prove it with the typecheck + e2e gate. Use when asked to "update dependencies", "are we on the latest", "do the quarterly sweep", "bump deps", or when the recurring sweep ticket comes due. We run NO update bot on purpose (#141) — this skill IS the update process.

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

Run the Playwright fixture smoke harness to prove a real generated crouton app still boots, authenticates, and does CRUD after a dependency bump or package change. Use when asked to "smoke test", "run e2e", "verify against a fixture", or to check that a packages/ change doesn't break consuming apps.

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

Scan code, dependencies, containers, IaC and SBOMs with Snyk via its first-party MCP server: authenticate, trust a folder, run the right scanner, read the findings, fix and re-scan. Includes package-health checks before adding a dependency.

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

Convert Claude's Markdown output to each channel's native text syntax before delivery. Adds zero-dependency formatting for WhatsApp, Telegram, and Slack (marker substitution). Also ships a Signal rich-text helper (parseSignalStyles) used by the Signal skill.

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

Convert Claude's Markdown output to each channel's native text syntax before delivery. Adds zero-dependency formatting for WhatsApp, Telegram, and Slack (marker substitution). Also ships a Signal rich-text helper (parseSignalStyles) used by the Signal skill.

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

Apply the "GitHub Actions and Renovate Guide" to configure repo settings, branch protection, GitHub App/PAT secrets, and renovate.json5 for personal or team GitHub projects. Use when asked to introduce Renovate, enable dependency auto-updates, or align settings with the guide.

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

Trace what an actual code change could break beyond its diff when interfaces, serialized data, database schemas, configuration, caches, lifecycle ordering, or cross-language consumers are involved. Use for explicit impact analysis; not local renames, prose edits, ordinary dependency bumps, or generic architecture discussion.

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

Plan or implement retirement of a system, API, feature, persisted configuration, or database shape. Use for compatibility cutovers, explicit deprecation review, or an explicit unreleased replacement decision, including determining whether consumers or data exist; not ordinary dependency bumps, local renames, prose edits, or generic architecture discussion.

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

Design, review, or report a measured performance comparison. Use for benchmark methodology, speedup or regression claims, and performance-based choices; not generic performance discussion, ordinary dependency bumps, local renames, or prose edits.

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

Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authenticat...

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

Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.

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

Turns requirements into a precise, dependency-aware implementation plan.

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

Investigate supply chain attack artifacts including trojanized software updates, compromised build pipelines, and sideloaded dependencies to identify intrusion vectors and scope of compromise.

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

Standard Operating Procedures for read-only codebase exploration, symbol search, dependency mapping, code tracing, code review, architecture analysis, technical research, source evaluation, and evidence-based reporting.

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

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

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

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

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

Break down implementation plans into actionable task lists. Use after planning to create a structured task breakdown. Generates tasks.md with ordered, dependency-aware tasks.

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

Update npm/yarn/pnpm dependencies using manifest-first, lockfile-aware workflows. Prefer declared version bumps over resolution overrides. Use when updating, upgrading, or patching dependencies; fixing transitive dependency versions; addressing npm audit or CVE findings; or removing stale overrides.

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

Defense-in-depth security across Rust, TypeScript, and Bash for the Pump SDK — cryptographic key handling, memory zeroization, secure file I/O, input validation, privilege management, dependency auditing, and a 60+ item security checklist.

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

Production-quality Bash scripts for Solana vanity generation, keypair verification, batch operations, dependency auditing, and test orchestration — with security-hardened patterns including file permissions, input validation, and cleanup traps.

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

Audit the project's documentation (CLAUDE.md, .claude/rules, skills, README, CONTRIBUTING, SECURITY, .env.example, app/data/*.md, learn articles) against the actual code and config, and fix drift. Use after refactors, dependency or workflow changes, or on a schedule.

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

Builds a DRAFT month-end, quarter-end or year-end close checklist and status table for a finance team from the close calendar, the open items list and last month's close issues that the user attaches, pastes or the agent can reach, marks every task on time, due, late, at risk or blocked, and flags dependency chains and repeat issues. Use when the user asks to "build the close checklist", "where are we on the month-end close", "what is late or blocked in the close", "refresh the close tracker as of today" or "prepare the close status note". Do not use for a project tracker or weekly project status, use project-status-tracker instead; for corrective actions from audits or NCRs, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

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

Work through which package to add for a capability, and what each option costs — maintenance, licence, bundle weight, transitive risk, and whether the platform already does it. Use when someone needs a library for a job and has not picked one yet, when weighing two candidates, or when a package looks convenient but unmaintained.

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

Package license analysis — detect copyleft conflicts against a permissive policy, surface AGPL / SSPL / GPL contaminants, output SPDX SBOM with per-package license findings. Use when auditing a release for license compliance, vetting a new dependency's license, building an OSS-attribution document, or producing a customer-facing license disclosure.

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