Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
Review VS Code release notes for style, structure, and completeness. Use for reviewing Insiders or Stable release notes against writing guidelines. Produces an actionable list of recommendations.
Run the Move Prover to formally verify specifications
Perform a local code review of the current branch's changes against Materialize project standards. Trigger when the user says "review my code", "review my changes", "check my diff", "does this look ok", "what do you think of this PR", "code review", or asks you to look over changes before merging. Also trigger when the user passes a PR number and wants feedback on quality, style, or correctness.
Run Python CLI tests. Use after making changes to cli/ code.
Perform comprehensive code reviews focusing on best practices, security vulnerabilities, performance optimization, and maintainability
Autonomous multi-round research review loop. Repeatedly reviews via Codex MCP, implements fixes, and re-reviews until positive assessment or max rounds reached. Use when user says "auto review loop", "review until it passes", or wants autonomous iterative improvement.
Autonomous multi-round research review loop. Repeatedly reviews using a secondary Codex agent, implements fixes, and re-reviews until positive assessment or max rounds reached. Use when user says "auto review loop", "review until it passes", or wants autonomous iterative improvement.
Autonomous multi-round research review loop. Repeatedly reviews using Claude Code via claude-review MCP, implements fixes, and re-reviews until positive assessment or max rounds reached. Use when user says "auto review loop", "review until it passes", or wants autonomous iterative improvement.
Check which Rust lines are not covered by Rust tests. Use this when you developed new Rust code and want to ensure it is tested.
Remove Rust-defined C symbols that are either unused or only used in C/C++ unit tests. Use this when you are refactoring a Rust FFI crate and want to remove unused symbols.
Review Rust code changes for unsafe correctness, documentation quality, and C-to-Rust porting fidelity. Use this when you want to review Rust changes before merging.
NetAlertX coding standards and conventions. Use this when writing code, reviewing code, or implementing features.
Review Azure SDK management-plane migration PRs (Swagger/AutoRest → TypeSpec). Checks customization quality, TypeSpec decorator usage, and migration-specific anti-patterns on top of the standard mgmt PR review.
Pre-commit validation checks for azure-sdk-for-net. Use this before committing or pushing changes to SDK packages. Runs dotnet format, exports public API listings, updates snippets, and regenerates code as needed.
A skill to review pending work for API design compliance in the
Use this skill to remove a feature flag when the flag is no longer needed and its current state must be made permanent. This skill provides a step-by-step workflow for safely removing obsolete feature flags and their associated dead code without introducing regressions or observable behavior changes.
Prepare language emitter changes for PR: validate (build, format, lint), add a changeset, and push. This skill is specifically for the language emitter packages (http-client-python, http-client-csharp, http-client-java) - NOT for core TypeSpec packages like compiler, http, openapi3, etc. Use when the user wants to finalize emitter changes, says things like "prep for pr", "prepare for PR", "validate and push", "add changeset", or "finalize changes".
