Hexclave — Visual PR Writeup
Capture screenshots from a running development site and prepare a pull request description with visual evidence.
These skills help an agent review code changes and respond to reviews. They cover full PR reviews, delta reviews, handling feedback, dependency PRs and writing clear PR descriptions.
56 skillsCapture screenshots from a running development site and prepare a pull request description with visual evidence.
Open or update a pull request in this repository, including writing or rewriting its description.
Scan React projects for correctness, accessibility, security, architecture and performance findings; triage and fix issues with the upstream workflow.
Review changes since the latest commit with incremental impact and blast radius analysis.
Review Renovate bot PRs that update GitHub Actions dependencies. Verifies supply chain integrity by checking pinned commit SHAs against upstream tagged releases, reviews changelogs for breaking changes, and confirms compatibility with existing workflow configurations.
Prepare a focused Tantivy pull request from staged changes with a generated commit message.
Review code changes using detected modifications and their effects on dependent code.
Organize and implement code-review feedback.
Read and triage existing pull request review comments, or address them when requested.
Review and improve SwiftUI state management, layouts, accessibility and performance, with Instruments trace guidance.
Review SwiftUI code for modern API usage, accessibility, data flow and performance.
Explain Git diffs or pull requests, affected components and potential change risks.
Install and update vendored Oxlint plugins that detect unwanted AI coding patterns while preserving a project's local rule customizations.
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
Audit and update npm/Bun dependencies with supply chain integrity checks — verifies maintainers, publish age, tarball diffs, and provenance before bumping. Defers risky packages to ~/.supply-chain/notes/.
Run an iterative worker-reviewer cycle for code, specifications or writing, with actionable feedback and a bounded review loop.
React Doctor workflows for scanning React code, planning fixes, inspecting Three.js and measuring runtime performance.
Reduce complexity while preserving exact behavior, project conventions and existing error handling.
Search for existing JavaScript and TypeScript symbols before adding potentially duplicate code.
Write and refactor Python with clear naming, short functions, flat control flow, and readable structure.
Apply task-oriented Rust guidance for ownership, error handling, async code, concurrency, API design, and code review.
Review or de-slop concrete changes in ccch1mneyyy/dsh-TUI at maintainer level: PR numbers or URLs, branches, commit ranges, patch files, staged or unstaged worktrees, and scoped repository-hygiene requests.
code-quality skill for Claude AI. Grade A. Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
Review code for security, correctness, performance, maintainability and testing gaps.
code-quality skill for Claude AI. Grade A. TypeScript standards and best practices with modern tooling. Use when working with TypeScript or TypeScript React files.
Turn systems, code changes and plans into visual HTML pages, diagrams and slide decks.
Simplify recently changed code while preserving behavior, using the project conventions and checking for duplicate helpers.
Ask one coding agent for a second opinion on a task while retaining ownership of the work.
Survey a React codebase and turn prioritized findings into implementation plans without editing application source.
Review, write and refactor NestJS applications using prioritized guidance on architecture, dependency injection, security and performance.
Review changes for correctness, readability, architecture, security and performance with actionable findings.
Write a pull request title and description using the project's preferred structure and change context.
Audit the repository or a broad subsystem for security, correctness, and maintainability risks.
Code comment hygiene for AI coding agents: remove generic AI-slop comments, keep the valuable ones, never touch the code.
Apply a disciplined software development workflow with test-driven changes, refactoring and code-quality tools.
Evaluate code-review feedback against the actual code before accepting, clarifying or challenging it.
Make the smallest complete change, with adjustable coding intensity and concise explanations.
code-quality skill for Claude AI. Grade A. Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring ...
Review diffs and pull requests, assess release readiness, and follow publishing steps.
Open Plannotator's browser-based code review UI for the current worktree, another directory, or a pull request URL, then act on the feedback that comes back.
Write concise code-review findings with location, problem and proposed fix.
Audit a codebase, prioritize evidence-backed findings, and write implementation plans for another agent or developer.
Review pull requests and branch diffs with graph context and a structured impact report.
Cross-examine non-trivial engineering decisions using fresh-context adversarial review and explicit stop conditions.
Audit a codebase for architecture, quality, security and testing issues.
Review a change and its connected code for correctness, safety, performance and unnecessary complexity.
Review a change against project standards and the originating specification using two review tracks.
Apply the core antislop rules alongside focused design, writing and code-comment workflows.
Compare code review skills for Git changes, graph context, focused findings and visual feedback. Choose a child workflow and give it a clear review boundary.
Use a full review skill for new PRs, a delta skill for follow-up commits, and feedback skills when you are the author responding to comments.