Loading...
Loading...
Found 127 Skills
Remove AI-generated code slop from a branch. Use when cleaning up AI-generated code, removing unnecessary comments, defensive checks, or type casts. Checks diff against main and fixes style inconsistencies.
Review only git diff for impact, regression, correctness, compatibility, and side effects. Scope-only atomic skill; output is a findings list for aggregation.
Request/execute structured code review: use after completing important tasks, at end of each execution batch, or before merge. Based on git diff range, compare against plan and requirements, output issue list by Critical/Important/Minor severity, and provide clear verdict on merge readiness. Trigger words: request code review, PR review, merge readiness, production readiness.
Analyzes git commits and changes within a timeframe or commit range, providing structured summaries for code review, retrospectives, work logs, or session documentation.
Generate clear, standardized git commit messages based on code changes (diffs), following Conventional Commits specification.
Optional skill. Reconstruct a human-review-preparation file from an existing pull request, merge request, branch diff, or commit range in a repository the user trusts. Use when the user wants retrospective understanding of already-implemented changes, AI-side assessment and recommendations, and an optional provider-specific sharing variant written to a local file when needed.
Re-reads code you just wrote with fresh perspective to catch bugs, errors, and issues. Use after completing a feature, fixing a bug, or any code changes. Triggers on "review my code", "fresh eyes", "check for bugs", "did I miss anything", or "sanity check".
Validate changesets in openai-agents-js using LLM judgment against git diffs (including uncommitted local changes). Use when packages/ or .changeset/ are modified, or when verifying PR changeset compliance and bump level.
You MUST use this, and not the upstream superpowers requesting-code-review skill, when completing tasks, implementing major features, or before merging to verify work meets requirements. The review itself runs the scrutinize-dispatch skill.
Technical solution evaluation and code review in the style of Linus Torvalds. Only use this when the user explicitly requests a Linus-style review or explicitly asks for a rigorous evaluation of code changes/technical solutions (e.g., "review changes/code", "evaluate if the solution is appropriate", "check submission standards", "linus-tech-review").
Validates code changes against DeepRead's mandatory patterns and standards defined in AGENTS.md. Use this after writing or modifying code to catch violations before committing.
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.