rex

Review technical documents and code against security, correctness, and design lenses.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/polkwagner/law-faculty-skills --skill rex-polkwagner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rex
Source: https://github.com/polkwagner/law-faculty-skills/tree/main/rex
Command: npx skills add https://github.com/polkwagner/law-faculty-skills --skill rex-polkwagner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and lenses (resource) components.

What problem does it solve?

This Skill provides a senior engineering perspective on technical documents and code, identifying potential issues and suggesting improvements before they become problems.

Core Features & Use Cases

  • Critical Review: Offers detailed and direct feedback on various technical artifacts like PRs, code, design specs, and more.
  • Security and Robustness Analysis: Focuses on identifying security vulnerabilities, maintainability issues, and design flaws.
  • Use Case: When you're about to merge a PR or release a new feature, you can use this Skill to ensure that your work meets the highest standards of quality.

Quick Start

Run the rex skill on the pull request with the identifier 'PR-123'.

Frequently Asked Questions about rex

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

FAQPage Schema
How do I review code and technical documents for security vulnerabilities?

Security analysis for technical documents and code is conducted by verifying the provided artifact against multiple predefined security, correctness, and design lenses. This approach identifies potential vulnerabilities, maintainability issues, and design flaws before merging pull requests or releasing new features.

Can I analyze a design spec or implementation plan before writing code?

Design spec and implementation plan analysis is fully supported. The review process evaluates architecture and PRDs using cross-cutting rigor to identify potential issues and suggest improvements, providing a senior engineering perspective before development begins.

What is the best way to review a pull request for design flaws?

Reviewing a pull request for design flaws is handled by applying cross-cutting rigor and predefined lenses to the code. This provides critical, direct feedback on the technical artifact to ensure it meets high software quality standards before merging.

Does this technical review process require any specific dependencies or environments?

No specific dependencies or environments are required to run this technical review process. The skill operates independently to analyze pull requests, code, and design specs using its internal scripts and lenses without external setup.

What types of technical artifacts can be evaluated using design review lenses?

Technical artifacts including pull requests, code, design specs, PRDs, implementation plans, and architecture documents can be evaluated. The review applies critical analysis to ensure robustness and software quality across all these formats.