Review pull requests in the Tenstorrent skills marketplace for plugin contracts, agent authorization, executable tooling, and trustworthy evaluation evidence. Use for changes to skills, supporting scripts, tests, or marketplace configuration in this repository.
Perform thorough code reviews with security, performance, and maintainability analysis. Use when user asks to review code, check for bugs, or audit a codebase.
Perform code review. Use for: (1) '/code-review' to review the current branch changes, (2) '/code-review PR #123' to review a specific PR, (3) '/code-review staged' to review staged changes, (4) requests such as 'review this code' or 'please review'.
Performs full defensive security reviews of software repositories for vulnerabilities, authorization flaws, insecure data flows, and missing security tests. Use when reviewing a repo, application, service, codebase, PR, diff, or implementation plan.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Review the changed code in the working tree against project conventions and common bug patterns. Use when the user asks for a code review, before committing, or before opening a PR.
Use when the user wants to review a file for bugs, antipatterns, or quality issues. Triggers on "review", "check for issues", "look for problems", "audit", "before I ship".
Evidence-based review of pull requests, branch comparisons, working-tree changes, or selected code across risk, repository standards, and originating requirements. Use when asked to review code, a PR, changes since a fixed point, or to coordinate an explicitly authorized review → repair → verify loop. Defaults to read-only.
Review code changes for correctness, conventions, performance, security, and test coverage. Use for: PR review, regression-risk analysis, Biome/TypeScript convention checks, API auth and validation review, block/tool contract audits, and severity-ordered findings.
Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.
153mo agoReviewMountCreate a free account to mount
Revisão holística pré-commit (estilo PR Review). Valida o diff contra as 3 memórias vivas, a spec da task e Clean Code, em paralelo ao QA/Security (fan-out); a evidência de teste é exigida no join. Executada pelo Tech Lead; veredito escrito em review.md.
Review pull requests in the SAP Testing Automation Framework. Use when reviewing a diff, a pull request, or staged changes touching platform code, Ansible roles and playbooks, custom modules, or the shell CLI. Reviews for correctness, reliability, security, Azure/SAP domain rules, performance, test coverage, and maintainability — in that priority order. Finds defects that let a validation report success without validating, accept a field and then discard it before it acts, break an object's stated contract, or leave one half of the SUSE/RHEL or HANA topology matrix unhandled.
Review diffs, commit ranges, fixup chains, or PRs across languages and report findings ordered by severity. Enforces primitive-obsession and smart-constructor blockers, property-test and boundary-test requirements, complexity thresholds and per-language rules (Rust, TypeScript, Lean, SQL, bash, Ruby, Markdown, regex). Delegates commit-history structure and repair to git-review. Also the home for changing review rules or codifying review feedback.
Use this skill when reviewing a PR diff, commit range, file change, or code snippet before merge. Reviews security vulnerabilities, code quality, style compliance, architectural integrity, test coverage, and performance; works with GitHub/GitLab diffs or raw code and produces a systematic, severity-labeled review.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.