5K skills · sorted by relevance
Analyze paid advertising reports from CSV files or connected accounts, explain performance, and recommend changes with monthly dollar amounts. Draft ad copy and visual briefs, then execute connected-account changes only after explicit approval for each one.
Navigate the Composio SDK monorepo, a repository containing multiple packages, and follow its shared development rules. Use it to decide where changes belong, handle generated files and release metadata, and prepare branches and pull requests.
Review completed code changes against the original requirements, choosing review depth by behavioral risk. Coordinate independent reviewers, resolve actionable findings, and verify that the delivered changes match the content actually reviewed.
Review FastGPT pull requests or local branch changes by examining actual code differences. Explain behavior changes and affected areas, identify unrelated changes, and report concrete concerns about code quality, consistency with nearby implementations, and missing test coverage.
Review recent code changes for duplication, maintainability, and wasted work, then apply straightforward improvements. The workflow combines three parallel reviews, prioritizes small, low-risk fixes, and checks the edited code with relevant tests or project checks.
Stage and commit code changes, push them to GitHub, and create or update a pull request, a request to review changes. Use the repository template and describe the motivation and final changes for reviewers.
Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.
Guide database structure changes in a project using Drizzle and node-pg-migrate. Covers generating and reviewing migration files, checking compatibility during deployment, handling indexes separately, and validating changes before applying them to shared databases.
Build and run computer-use-demo in Docker, then use Playwright to test its Streamlit interface without opening a visible browser. Save conversation transcripts, API exchanges, and screenshots to inspect behavior after changes.
Guide a Verdaccio change through a pull request, from branch preparation and checks to changelog entries, labels, CI results, and review responses. Track separate pull requests when the fix also belongs on other release lines.
Review recent Git commits to find changes that affect users, then update the relevant documentation pages. Identify missing pages, explain changed behavior or migration steps, and validate the resulting documentation with the project's build tools.
Review merged pull requests and significant commits within a release window, then organize features, fixes, breaking changes, and security signals into structured source material for drafting release notes.
Review Apache DataFusion pull requests using the project's review guide. Gather the proposed changes, discussion, and automated check results, or apply the same review criteria to your own changes before submitting a pull request.
Distribute edits across the appropriate branches in a Graphite stack, a chain of dependent branches. Use manual grouping when automatic absorption misplaces changes, then update commits, resolve restack conflicts, and verify the affected branches locally.
Run an AI vulnerability scan on uncommitted changes, changes against main, or an entire codebase. Filter candidate files, investigate potential security issues, and review findings with severity ratings, with options to revalidate and export results.
Review Git code changes using the CodeRabbit CLI. Receive a summary of the changes and issues ordered by severity, with affected file paths, practical impact, and concrete suggestions for follow-up fixes.
Prepare local iPolloWork changes for GitHub while staying on the current personal branch. Preserve edits, sync from main, report conflicts, commit and push changes, and create a pull request when requested.
Review code changes for concrete defects. Use it to examine modified code when you want to check whether a change contains a bug, with the review focused on specific problems in the changes.
Read staged Git changes and suggest a message in Conventional Commits format, a structured way to describe changes. Include a concise subject and relevant details, then request confirmation before creating the commit.
Use Git changes to generate Conventional Commits messages, a format that labels each change by type, and create commits. The skill suggests splitting unrelated changes and supports explicit scope, type, sign-off, and amendments to the previous commit.
Create a GitHub pull request from the current branch with a structured title, a clear explanation of behavior changes, and recorded check results. For UI changes, attach before-and-after screenshots so reviewers can assess the visual differences.
Review uncommitted changes, commits, branch differences, or pull requests in context. Identify bugs and concrete security weaknesses, explain when each issue occurs and how serious it is, and provide actionable feedback grounded in the surrounding code.
Upgrade an existing .NET 10 project to .NET 11 by updating framework targets and packages, fixing compatibility issues, reviewing runtime behavior changes, and verifying builds, tests, and deployment configuration.
Detect unusual changes in Google and Meta advertising performance by comparing current metrics with recent averages. Get issues ranked by estimated financial impact, likely causes supported by related changes, and recommended immediate actions.