skills.rest
alastor0325
alastor0325COMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Orchestrate multi-aspect Firefox patch reviews into structured documents.

Updated Jun 3, 2026
Search Tags:#automation#security#review#patch#code-review#phabricator#firefox
One-click install
npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill review-alastor0325
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/alastor0325/fx-bug-toolkit/tree/main/skills/review
Command: npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill review-alastor0325

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes patch reviews for Firefox by orchestrating multi-aspect analysis, routing tasks to specialized reviewers, and producing a structured, auditable review document.

Core Features & Use Cases

  • Orchestrated multi-aspect reviews: spec, security, threading, code-quality, and tests, with optional IPC, error-handling, and API-usage scopes.
  • Adversarial verification: coordinates follow-up verification to validate findings and strengthen review confidence.
  • Structured output: writes a formal review document in the review directory that records findings, evidence, and remediation suggestions.

Quick Start

Initiate a review by applying the /review command to a patch to generate a structured document.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Firefox patch code reviews for security and threading?▼

Automate Firefox patch reviews by orchestrating specialized per-aspect reviewers for security, threading, spec, code-quality, and tests to synthesize findings into a structured document.

What is the best way to coordinate multi-aspect patch reviews in Phabricator?▼

The best way to coordinate multi-aspect patch reviews is by routing patches to specialized reviewers and performing adversarial verification to produce an auditable review document.

How does adversarial verification work during a code review?▼

Adversarial verification works during code review by coordinating follow-up checks that validate serious findings and strengthen overall review confidence before finalizing the document.

When do I need IPC and error-handling scopes for a Firefox patch review?▼

You need IPC and error-handling scopes for a Firefox patch review when the patch touches relevant areas, triggering the routing of reviews to these additional dimensions.

Does this automated review process handle untrusted data safely?▼

Yes, the automated review process handles untrusted data safely by enforcing strict security rules throughout the synthesis of findings, evidence, and recommended fixes.

Where are the final Firefox patch review findings and evidence written?▼

The final Firefox patch review findings, sources, evidence, and recommended fixes are written to the designated FX_REVIEW_DIR as a structured formal document.

Related Skills

Explore More Software Engineering Skills→
ChunMinChangChunMinChang

create-patch

Automate Firefox patch and commit drafting with context gathering and message generation.

Community
Intermediate
jpoleyjpoley
50

patch-engineer

Validate security patch quality and regression risk for code changes.

Community
Advanced
matteocervellimatteocervelli
25

typescript-quality-checker

Validate TypeScript/JavaScript code quality with Prettier, ESLint, tsc, and npm audit.

Community
Advanced
ysyecustysyecust
40

springboot-verification

Verify Spring Boot projects with builds, static analysis, tests, and security scans.

Community
Advanced