5.7K skills · sorted by relevance
Get critical feedback on research ideas, papers, and experimental results from an external AI reviewer. Repeated discussions help identify unsupported claims, plan missing experiments, and document agreed improvements with priorities and estimated computing costs.
Run repeated reviews of research work, implement fixes, and request another assessment for up to four rounds by default. The workflow records progress and stops when both the review score and verdict meet its acceptance rules.
Review selected files for bugs by reading full source code, callers, and related implementations. Apply detailed checklists and investigate suspected issues, then report evidence, confidence levels, and suggested fixes.
Run repeated code reviews and fixes using an installed reviewer chosen by the user. The workflow tracks findings across rounds, checks that edits stay within scope, and reports whether blocking issues were resolved or further decisions are needed.
Support shellcode development for security testing: small machine-code programs executed in memory. The skill covers x86/x64 implementation, code that works regardless of its memory address, loaders, executable conversion, debugging, and platform-specific execution constraints.
Updates Claude Code CLI release tracking within the Claude Code Ultimate Guide, following its documented workflows. It can also handle an explicitly requested guide version bump and report changes, verification results, and unresolved checks.
Review code changes for concrete defects. Use it to examine modified code when you want to check whether a change contains a bug, with the review focused on specific problems in the changes.
The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; on the default branch it reviews the unpushed and uncommitted work. A bug-hunting code review complements this review and does not replace it. Also use for 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Takes an optional path, tag, topic, or ref in free text; no first word is a mode — say 'are docs out of date', 'audit the knowledge base', 'close out the feature', or 'capture this pattern' in plain words. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.
The English summary is being prepared. Showing the original description.
The art of reviewing code that improves both the codebase and the developer - sharing knowledge, maintaining standards, and building cultureUse when "code review, PR review, pull request, merge request, review comments, LGTM, review feedback, approve PR, request changes, review checklist, code quality, review standards, code-review, pull-request, PR, quality, standards, feedback, collaboration, mentoring" mentioned.
The English summary is being prepared. Showing the original description.
Hand off code review to OpenAI Codex CLI. Use when asked to "review code with codex", "codex review", "get a second opinion on code", "review my changes", "review this PR", or when you want AI-powered code review from a different model perspective.
The English summary is being prepared. Showing the original description.
Review code for quality, bugs, and design issues. Use when the user says "review this code", "do a code review", "check this PR", "review this diff", "is this code good", "what's wrong with this code", "code quality check", or pastes code and wants feedback - even if they don't explicitly say "code review".
The English summary is being prepared. Showing the original description.
Monitor PR review comments and automatically classify and address reviewer feedback including code changes, questions, and nits. Use when handling PR reviews, addressing reviewer comments, responding to code review feedback, or automating review resolution. Triggers on handle reviews, PR review, address feedback, reviewer comments, code review, review response.
The English summary is being prepared. Showing the original description.
Check skills before distributing them to Codex or Cursor. Identify unsupported metadata fields, Claude-specific variables in shell examples, and inconsistencies between source skills and their installation copies using the project's compatibility checker.
Delegate feature implementation, refactoring, and pull request reviews to OpenCode CLI, a command-line AI coding agent. Run bounded tasks or ongoing sessions, monitor progress, resume work, and report file changes and test results.
Review code changes without modifying files, checking surrounding code, tests, and callers for defects introduced by the change. Receive actionable findings ranked by severity, with precise file locations and a brief assessment of remaining risks.
Review code changes before merging across correctness, readability, architecture, security, and performance. Get findings that distinguish required fixes from optional suggestions, with concrete ways to simplify code and checks on test coverage.
Monitor a specific Vercel deployment in Codex and report when it becomes ready or fails. The skill identifies the exact deployment, checks its recorded state, and includes dashboard and preview links in the notification.
Turn local Claude Code session history into a personal activity report, cross-checked with local Git history. Generate Markdown and standalone HTML showing project activity, touched files, related commits, and each project's share of compute usage.
Organize parallel code reviews across security, performance, architecture, testing, and accessibility. It helps assign review areas, merge duplicate findings, apply consistent severity ratings, and produce one report with locations, impacts, suggested fixes, and prioritized actions.
Plan Codewhale changes by locating the existing implementation and its callers, defining one reviewable change, and choosing verification before editing. Use it for features, upgrades, and refactoring to avoid duplicate implementations and unfinished migrations.
Break a large development brief into ordered goals and save plans, progress events, blockers, and evidence in the repository. Coordinate Claude Code sessions through handoff instructions, with final completion requiring cleanup, verification, and code review evidence.
Check active PUA agents and teams from Codex CLI using an alias for the Claude Code status command. Review process IDs and record lifetimes when available, alongside stale records.
Stress-test a paper with a focused rejection argument, then have a separate reviewer assess each objection against the current text. The report identifies unresolved weaknesses, their severity, and priority fixes for submission or rebuttal preparation.
Use MiniMax to review research, address weaknesses through code changes, experiments, or analysis, and request another assessment. The workflow runs up to four rounds and preserves reviewer responses, actions, results, and unresolved blockers.