Results for “review-queue”

Use to find where support routing is failing — misrouted contacts, reassignment chains, unassigned work, and queues nobody owns. Trigger for "why do tickets bounce between teams", "are we routing correctly", "tickets sitting unassigned", "how many tickets get reassigned", ticket ping-pong, or reviewing routing rules and queue design.

`task-agent`/`review-agent`: use when jobs, workers, queues, schedules, retries, cancellation, or status visibility need design; skip when no async-job decision is required.

Routes rendered UI testing, visual regression, browser QA, accessibility, responsive, performance, or frontend review to a leaf skill.

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish". Proactively suggest when the user mentions visual inconsistencies or wants to polish the look of a live site. (gstack)

Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.

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

Seven-role depersonalised panel review of framework artefacts (KUD, criterion bank, LT definition, crosswalk, scope-and-sequence) in sequential-isolation mode. Gate rule mean>=88 AND no role<70.

Aggregate cross-asset quality control for campaigns. Use when the user requests 'run QC', 'quality check campaign', 'review all assets', or 'generate QA report'.

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

Review a ticket or PR through focused specialist lenses: scope, architecture, security, tests, AC coverage, and PR metadata.

通用跨模型审查：Review LLM 对任意研究制品进行独立评审，输出结构化评分、wiki 实体映射与改进建议

Benchmark-relative quality gate. Scores the draft against the research dossier's beat spec (depth, consensus coverage, evidence) plus AI-tell and voice signals, runs an adversarial read armed with the SERP benchmark, and emits the verdict that gates the pipeline.

QA Testing

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

Audit and implement behavior-preserving cleanup across types, dead code, dependencies, errors, and comments

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.

Use when a skill needs the user to interactively review code changes in revdiff mid-workflow — working changes, staged changes, or a specific commit — then read their annotations back. Takes a review mode.

Perform thorough code reviews on files or pull requests, checking for bugs, security vulnerabilities, performance issues, and style violations. Use when the user requests code review or provides relevant inputs for this workflow.

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.

Review this PR or diff for quality, security, and maintainability. Use when reviewing pull requests, examining a named change set, or the user asks for a code review of current work. Repo-wide anti-patterns → audit-code-quality. Bulk transform semantics → audit-codemod-safety.

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.