Results for “review-queue”

WelineFramework queue diagnostics and operations guide. Use when working on Weline\Queue, queue CLI commands, queue registration, queue_id/biz_key lookups, w_query('queue', ...) CRUD/stat queries, or failures involving queue:collect, queue:run, QueueInterface, and framework queue rows.

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)

Iterate on a pull request until actionable CI checks pass and high/medium review feedback is addressed, stopping at human approval, draft, or merge gates.

Use to design support queues and the skill taxonomy routing rules depend on — not as an org chart mirror, but as staffable combinations of skill, priority and channel. Trigger for "how should we structure our queues", "too many queues", "queue design", "routing taxonomy", "catch-all queue growing", overflow rules, or redesigning queue structure before changing routing rules.

Reviews local git changes and GitHub pull requests, leaving inline comments and formal reviews.

PR Fleet

QA Testing

Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.

Load this skill when the user says "review issue", "review-issue", or "/review-issue". Reviews an implemented GitHub issue against its requirements and the project coding standards, acting as a critical tech-lead review pass before merging.

Provides a structured workflow for unit, integration, E2E, and performance testing, including browser automation, code review, and quality gates.

Temporarily turn off the requirement that pending changes be reviewed before committing in the current herdr workspace.

Review pull requests against repository standards using automated validation and manual content review.

Automates end-to-end QA: starts the app, exercises screens and API endpoints, verifies functionality and design quality, runs domain analysis, and fixes issues found.

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

Runs a multi-perspective review of a pull request, including code quality, tests, and potential silent failures, then reports findings ranked by severity.

Check whether Claude Code CLI is ready in this environment and optionally toggle the stop-time review gate. Args: --enable-review-gate, --disable-review-gate. Use for installation, authentication, or review-gate setup requests.

Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.

Review a pull request and POST the review to GitHub via `gh pr review`. Use when asked to review a PR, or when the github-activity poller fires a PR-opened / PR-review-requested event. Always submits after drafting — a review that stays in turn output and never reaches GitHub is a non-review.

Use to staff and schedule QA reviewers for sustainable throughput without grading quality collapsing — fatigue, drift, and false precision from treating reviewers like production agents. Trigger for "how many QA reviewers do we need", reviewer capacity planning, grader fatigue, throughput per reviewer, calibration after long shifts, or scores drifting over the course of a day.

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

Runs a structured code review as a pre-commit or pre-ship gate, supporting multiple review engines and scope governance.

Establish design review gates with criteria, checklists, and approval workflows to maintain design quality.

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose review.

Systematically QA test a web application and fix bugs found. (gstack)

queue-usage

Reviews code diffs or explicit file sets through independent correctness and QA lenses, producing a severity-ordered verdict for pre-merge audits or review gates.

Waits for Copilot to review a PR and automatically chains the fix-comments cycle, up to two rounds. Use right after opening a PR with `ship`, and whenever the user says "wait for the review", "let me know when Copilot answers", "keep going with the PR", or asks to leave the PR review cycle running — or in Spanish "quedate esperando el review", "avisame cuando Copilot conteste", "seguí vos con el PR".

Self-contained code review checklist — formatting, type safety, duplication, readable conditions, logic-out-of-UI, test coverage, comment quality. Adapts to whatever tooling the project actually has (skips Prettier/TypeScript/test-runner checks if unconfigured). Use before merging, after completing a feature, or any time you want a second pass on code quality. In Claude Code, prefer the official `code-review` skill or `pr-review-toolkit`/`feature-dev` code-reviewer agents instead — both are real, installed, and go deeper than this checklist. This copy exists for Codex/Cursor portability, where those agents aren't available.

Use this skill for code review and PR review tasks. Covers review methodology, what to flag, what to skip, and output structure.

Dispatch a code reviewer subagent to catch issues before they cascade, with precisely crafted context for evaluation.

Routes quality reviews to specialized critic agents based on file type or flags, covering peer review, code review, and manuscript polish.

Selects and reviews Queueable, Batch, Future, and Schedulable Apex for callouts, large data processing, retries, and background work, with decision guidance and validation checklists.