5.1K skills · sorted by relevance
Compare code changes since the latest Git tag with English, Chinese, and Japanese documentation. Update affected guides and CLAUDE.md, check links and contents pages, or report inconsistencies without changing files.
Accept screenshot baseline changes by running the project's dedicated script, then commit the updated version.json using the project's commit conventions. This provides an explicit command for recording changes to the screenshot comparison baseline.
Validate changes to Squad coordinator and agent templates through real sessions using a locally built CLI. Check generated files, agent behavior, and saved state, then record evidence, scenario verdicts, and progress for pull request reviews.
Verify OpenMausBot server and conversation changes in an isolated instance using a fake engine, a stand-in for the real engine. Follow the canonical verification guide and shared control tool to check supported server workflows before reporting success.
Track changes during authorized red-team testing by comparing response times, headers, and account lockouts. Preserve evidence before and after changes, investigate possible defensive actions or concurrent attacks, and turn observations into timestamped findings.
Review concrete code changes for defects, compatibility problems, repository-rule violations, and unnecessary code. Produce evidence-based findings and, when explicitly requested, make minimal cleanup changes while checking that existing behavior is preserved.
Draft release notes that explain what changes for users. Verify the release range, reconcile commits and reversals, and highlight breaking changes, migration steps, and relevant pull requests with evidence.
Validate substantial Rust changes by running the repository’s prescribed checks in order. Handle check failures, review formatting changes, and report which commands ran and whether validation passed before handing the work back.
Check assumptions before changes to APIs, pricing, quotas, or defaults. This skill combines research, measurements from real services, documented results, and product-owner approval to assess customer impact beyond passing tests, with follow-up verification after deployment.
Classify how a pull request affects documentation using its changes and a documentation index. Return a JSON verdict identifying whether updates are unnecessary, already covered, needed within existing pages, or require structural changes.
Synchronize CS-Notes changes between local files and Git remotes while preserving unpublished materials. Reconcile material records, validate public changes, and commit and push updates, with separate options for inspection or pull request creation.
Review the final set of code changes for a LoopX goal, check reuse and simplification, and record validation results in a quality receipt tied to the exact changes being delivered or merged.
Turn git history since a release tag or specified reference into clear App Store release notes. Identify user-visible changes, remove duplicates and internal maintenance work, and draft concise bullets that explain what changed for users.
Draft huggingface_hub release notes from saved pull request JSON files. The skill groups changes, explains major updates, adds examples from documentation changes, and includes author credits and verified documentation links in a Markdown document.
Try model or training changes in a copied Grug or Grugformer experiment, document the differences, and bring successful changes back into the base template while removing superseded experiment code and checking behavior.
Preview pending infrastructure changes in a specified Marin Pulumi stack without applying them. Trace each change to supporting code and merged pull requests when deployment history provides a reliable Git baseline.
Track changes to recommendation, moderation, and monetization rules across six Chinese social platforms. Get a dated report with source links, creator impact, and practical responses, clearly distinguishing official announcements from unverified community observations.
Route requests to commit, push, or save Git changes through a dedicated /commit skill. The workflow removes Claude attribution, records attempted approaches in reasoning.md, clears build attempts, and pushes changes when requested.
Run final checks after reviewed SDK changes, covering dependency installation, builds, types, generated declarations, linting, tests, and formatting. The workflow requires every check to pass before the work is marked complete.
Turn the actual task changes into an English PR title, description, and branch name suggestion. Include relevant committed and uncommitted work, explain the motivation and behavior changes, and prepare text ready to paste into GitHub.
Review a JavaScript SDK release plan or final candidate against the previous release. Check compatibility, packaging, regressions, and Changesets version records, then recommend shipping or blocking with supporting evidence and a separate assessment of documentation coverage.
Cleans redundant comments, dead code, duplication, and unnecessary complexity from branch changes or selected files. Establishes passing regression tests first, then checks that cleanup preserves existing behavior and public APIs using the project's quality tools.
Create, edit, and inspect Word documents, including text extraction, formatting, comments, and tracked changes. Its review workflow marks only the text that changes, helping reviewers identify revisions while preserving unchanged content and formatting.
Create, edit, and examine Word documents while preserving formatting. This skill supports text extraction, comments, and tracked changes, helping agents prepare new documents and make precise revisions that reviewers can inspect.