1.1K skills · sorted by relevance
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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".
The English summary is being prepared. Showing the original description.
Manage third-party libraries, runtimes, and SaaS dependencies. Use this skill when setting an update cadence, responding to security advisories, dealing with deprecated dependencies, evaluating new dependencies, auditing what's installed, or unblocking a dependency upgrade. Triggers on dependency, package update, security patch, lockfile, deprecated, breaking change, supply chain, dependency audit, npm audit, dependabot, renovate. Also triggers when a build breaks after an update or when an advisory is published for a used package.
The English summary is being prepared. Showing the original description.