Official · PrismaFreeSummary Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.
- Updating Biome to a specified version
- Aligning configuration files after dependency updates
- Checking for issues introduced by a Biome update
prisma/orm☆ 47.7KUpdated Oct 21, 2026
Monitor selected GitHub Actions checks on an SGLang pull request until they pass on its latest commit. Diagnose failures, push small validated fixes, and retry only failed jobs within defined limits.
- Monitor selected PR checks until they pass
- Separate code failures from infrastructure problems
- Apply small fixes and track the resulting checks
sgl-project/sglang☆ 37.6KUpdated Oct 21, 2026
Assess skills CLI pull requests for focused bug fixes using visible patches and regression tests. Surface well-supported candidates with a label and brief maintainer comment, while keeping uncertain findings out of public updates.
- Identify well-supported bug-fix pull requests
- Check regression tests and effects on other supported agents
- Suggest possible matching issues from available board findings
vercel-labs/skills☆ 35.9KUpdated Oct 20, 2026
Diagnose and repair GBrain’s Postgres access with a fixed recovery command. Apply routine fixes, request approval for configuration rewrites, and verify connectivity afterward. Credential problems and other manual cases are returned with instructions for the operator.
- Diagnose GBrain database connection failures
- Apply routine fixes such as reconnecting or pending migrations
- Review and approve connection configuration rewrites
garrytan/gbrain☆ 31.1KUpdated Oct 21, 2026
Repair an entire broken feature by mapping its files and dependencies, checking configuration and logs, and confirming root causes. Apply fixes in sequence, then test the feature and the code that uses it.
- Repairing a broken feature from start to finish
- Investigating imports and configuration together
- Finding root causes across multiple modules
alirezarezvani/claude-skills☆ 28.5KUpdated Aug 30, 2026
Prepare a game's launch day patch by selecting known bugs that are safe to fix quickly. Coordinate minimal fixes, verify affected areas, and document deferred issues, quality checks, rollback procedures, and patch notes.
- Selecting known bugs for a launch day patch
- Planning minor fixes from platform certification feedback
- Verifying fixes and checking affected game systems
Donchitos/Claude-Code-Game-Studios☆ 27KUpdated Oct 19, 2026
Collect new feedback from configured Slack and GitHub Issues sources, acknowledge receipt, analyze recordings, and verify claimed fixes against the default branch. Combine unresolved items into a rolling plan ready for the lfg workflow.
- Collecting feedback from Slack and GitHub Issues
- Analyzing recordings attached to feedback
- Verifying that reported fixes were merged
EveryInc/compound-engineering-plugin☆ 25.6KUpdated Oct 21, 2026
Delegate checks for AGENTS.md rule violations to a dedicated agent. It scans the codebase, fixes high-impact issues in a separate working copy, runs full validation, and creates a pull request, tracking progress across runs through memory.
- Checking code for AGENTS.md rule violations
- Prioritizing high-impact rule violations for fixes
- Checking compliance within a chosen focus area
coleam00/Archon☆ 23.7KUpdated Oct 21, 2026
Continuously monitor automatic end-to-end tests on NemoClaw main, group failures by root cause, and coordinate fixes and peer reviews through GitHub. Track ownership and merge readiness while checking whether later runs confirm each repair.
- Continuously monitor automatic test failures on main
- Coordinate repair ownership across maintainers
- Review peer fixes and assess merge readiness
NVIDIA/NemoClaw☆ 22.8KUpdated Oct 21, 2026
Create changelog files for significant changes in a pull request, a proposed code change. Describe effects users will notice and organize entries by PR number and change type, such as features or fixes.
- Writing changelog entries for a pull request
- Separating new features from bug fixes
- Explaining changes in user-facing language
pipecat-ai/pipecat☆ 16.7KUpdated Oct 21, 2026
Turn scan data into a categorized release notes draft covering features, fixes, breaking changes, and security. Get clean Markdown suitable for a CHANGELOG or GitHub release, with a review disclaimer and human approval required before publication.
- Draft release notes from scan results
- Organize features, fixes, breaking changes, and security updates
- Prepare Markdown for a CHANGELOG or GitHub release
cobusgreyling/loop-engineering☆ 11.6KUpdated Oct 21, 2026
Prepare a bug-fixing run by recovering reproduction details and tests, checking the workspace, and finding existing fixes. Select the appropriate workflow for a reproduction session, CI run, bug ticket, or requested PR changes.
- Recover reproduction tests from a session or CI run
- Check the workspace before starting a bug fix
- Find existing fixes before choosing an approach
omnigent-ai/omnigent☆ 11KUpdated Oct 21, 2026
Official · OpenClawFreeSummary Combine Convex authorization, code quality, performance, and failure audits into one readiness report. It removes duplicate findings, scores confirmed issues with a stated formula, and orders the fixes while clearly identifying checks that could not run.
- Reviewing a Convex app before launch
- Combining audit findings into one report
- Prioritizing authorization and performance fixes
openclaw/clawhub☆ 9.5KUpdated Oct 21, 2026
Official · OpenClawFreeSummary Review 72 hours of Convex deployment health events and trace read limits or conflicting writes to the responsible code. Receive prioritized performance, cost, and reliability findings with runtime evidence, source locations, and concrete fixes.
- Investigating read limits and large table scans
- Tracing conflicting writes to shared records
- Reviewing deployment performance and cost issues
openclaw/clawhub☆ 9.5KUpdated Oct 21, 2026
Group bug reports by their underlying cause and plan shared fixes. This skill guides reproduction, checks for unnecessary complexity, and requires named test evidence before treating related issues as resolved.
- Grouping accumulated bug reports by root cause
- Planning one fix for several related issues
- Checking test evidence before closing issues
Gentleman-Programming/gentle-ai☆ 7.9KUpdated Oct 21, 2026
Run repeated code reviews and fixes using an installed reviewer chosen by the user. The workflow tracks findings across rounds, checks that edits stay within scope, and reports whether blocking issues were resolved or further decisions are needed.
- Repeat reviews and fixes for a module
- Improve code using a specific installed reviewer
- Keep automated edits within an agreed file scope
trailofbits/skills☆ 7.7KUpdated Oct 21, 2026
Runs repeated reviews and fixes on a Claude Code skill until no critical or major findings remain. Tracks findings across rounds, checks change boundaries, and stops for a design decision when fixes stop making progress.
- Refining a skill until critical and major findings are resolved
- Improving skill metadata, trigger descriptions, and references
- Tracking recurring findings across review rounds
trailofbits/skills☆ 7.7KUpdated Oct 21, 2026
Organize unresolved feedback on GitHub pull requests, group changes by file or behavior, and apply selected fixes locally. Run relevant tests and summarize completed work and remaining issues, with replies and thread resolution requiring explicit user direction.
- Organizing unresolved pull request feedback
- Applying selected review fixes locally
- Testing changes and summarizing remaining issues
Devin-AXIS/iPolloWork☆ 7.1KUpdated Oct 20, 2026
Compare a website with supplied references to identify originality risks in text, images, videos, layout, motion, and code history. Produce evidence-backed findings and practical fixes while distinguishing common design patterns from distinctive copying.
- Review a site against its references before release
- Check text and media for distinctive overlaps
- Find copied material in repository history
MengTo/Skills☆ 6.9KUpdated Oct 18, 2026
Interpret n8n validation results and fix configuration, connection, and expression issues. Distinguish blocking errors from warnings and known false positives, choose suitable validation settings, review automatic fixes, and test actual outputs after structural checks pass.
- Understand and fix workflow validation errors
- Distinguish known false positives from real warnings
- Preview and select automatic workflow fixes
czlonkowski/n8n-skills☆ 6.5KUpdated Oct 16, 2026
Analyze Google Ads Quality Score, a keyword-level quality rating, across expected click-through rate, ad relevance, and landing page experience. Identify weak components and their causes, then prioritize fixes by potential click-cost savings and conversion impact.
- Monthly reviews of keyword Quality Scores
- Investigating unexplained increases in click costs
- Checking quality changes after landing page updates
irinabuht12-oss/marketing-skills☆ 5.2KUpdated Oct 13, 2026
Write and review R analysis scripts for a sewage research project using its established conventions. Estimate requested regression models, add specifications, and save LaTeX tables, figures, and model objects for use in the research paper.
- Estimate models of sewage spills and property prices
- Add specifications to an existing regression analysis
- Create descriptive plots and maps
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4.7KUpdated Oct 20, 2026
Review unresolved GitHub pull request comments against the current code, apply minimal fixes for valid issues, and reply to review threads. Comments that need human judgment remain open, while fixed or unnecessary requests are resolved with explanations.
- Addressing unresolved pull request reviews
- Checking whether review comments still apply
- Separating fixes from requests needing human review
IvanMurzak/Unity-MCP☆ 4.5KUpdated Oct 20, 2026
Investigate reproducible bugs by recreating symptoms, testing one possible cause at a time, and checking fixes in both a simplified test case and the original scenario. Retry limits keep unsuccessful fixes from continuing unchecked.
- Investigating a reproducible bug
- Checking a fix in the original scenario
- Reconsidering causes after failed fixes
nyldn/claude-octopus☆ 4.3KUpdated Oct 21, 2026