5.1K skills · sorted by relevance
Assess an existing Verdaccio pull request by checking code changes, automated checks, review feedback, release notes, and supported release branches. Receive a verified report explaining whether it is ready to merge and what needs attention.
Review Verdaccio code changes for security, package manager compatibility, performance, and maintainability. Verify concerns against surrounding code and relevant tests, then report actionable issues with their location, trigger, impact, and supporting evidence.
Implement Verdaccio fixes, features, or refactoring after checking whether existing settings or plugins already solve the problem. Place changes in the responsible component, reuse helpers, add tests and release notes, and validate affected packages.
Investigate a codebase, reproduce bugs, implement requested changes, and verify the results using Leon’s file, search, and shell tools. Follow project instructions, preserve existing user changes, and report checks and unresolved issues.
Coordinate Stripe pricing changes, Supabase database updates, and Vercel deployments through the Composio CLI, a command-line tool. Follow an ordered release workflow with post-deployment checks, Slack announcements, and guidance for reversing changes if verification fails.
Draft or update GitHub pull request descriptions using the actual changes and related context. Explain the problem, changed behavior, and review concerns in plain language, including breaking changes and explicit issue-closing references when applicable.
Inspect GitHub and GitLab repositories, issues, and proposed code changes, then prepare small fixes with tests and review summaries. Uses existing command-line authentication and requires approval before publishing changes or modifying repository records.
Review tRPC API changes against released desktop, mobile, CLI, and SDK clients. Use release history and usage data to choose compatible changes, assess whether deprecated features can be removed, and plan recovery when deployed changes break clients.
Scans merged pull requests and commits since a chosen reference, using titles, labels, milestones, and messages to categorize changes. Produces a release notes draft, highlights breaking changes and security items, and records the scan window.
Scan recent merges, pull requests, and commits for release note material. Produce structured entries and a summary with PR references, highlighting breaking changes and security items while filtering routine dependency and bot noise.
Scan merges and commits since the previous release to collect user-facing changes for a changelog. Produce structured entries and a summary, with explicit lists of breaking changes and security signals.
Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.
Explain code structure and behavior with text diagrams, including before-and-after views of changes. Trace data flow and state changes, clarify design choices, and examine assumptions, possible failures, and interactions between tasks running at the same time.
Record dated developments in litigation matters and update the corresponding matter log. Capture status, risk, deadlines, and settlement developments, with proposed history entries and field changes shown for review before saving.
Review proposed updates to legal practice guidelines one at a time, record decisions, and inspect exact changes before approval. Accepted or edited proposals update the practice profile only after an attorney explicitly confirms them.
Guide changes and reviews in datafusion-ffi, which connects separately compiled libraries. Check binary compatibility, memory ownership, and method coverage, and choose unit and cross-library tests for new wrappers, trait extensions, or codec changes.
Investigate why TypeScript uses a particular built-in type by tracing issues, proposed changes, and team comments. Produces a linked timeline and explanation of past trade-offs to help assess type overrides in ts-reset or proposed typing changes.
Assess test strength by introducing deliberate code changes with mewt or muton. Configure test runs, examine changes that tests miss, distinguish harmless equivalents from testing gaps, and investigate potential bugs in the affected code.
Compare Sentry issues across selected time windows and releases to find new or recurring problems and changes in frequency or affected users. Prioritize findings using user impact and the strength of available evidence.
Publish selected local changes to GitHub by checking their scope, creating a branch when needed, committing files, and pushing them. Create a draft pull request, a proposed change awaiting review, and report checks and remaining risks.
Create, edit, and analyze Word documents while preserving formatting. Work with tracked changes and comments, extract document text, and convert pages to images for visual review, with workflows tailored to new documents and existing files.
Plan substantial DeepChat changes with a written design proposal and a clear implementation path. Record decisions, track progress, review the completed change, and select focused validation for features, complex bugs, or architecture updates.
Review Apache Pinot changes for correctness in null handling, numeric types, type-based processing, and resource lifecycles. Use it to examine changes to calculations, aggregations, window functions, and segment cleanup or persistence.
Review the scope and process of Apache Pinot changes, including pull request descriptions, reverts, retries, and compatibility notes. Use it to examine large changes, test workarounds, and documentation needed for changes that break backward compatibility.