forgex-review

Identify defects, regression risks, and missing links in Forgex code reviews.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/codernai14-source/Forgex --skill forgex-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forgex-review
Source: https://github.com/codernai14-source/Forgex/tree/main/.cursor/skills/forgex-review
Command: npx skills add https://github.com/codernai14-source/Forgex --skill forgex-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forgex code review skill helps identify real issues such as bugs, regression risks, link gaps, and omissions during code review, debugging, PR reviews, or user requests for review.

Core Features & Use Cases

  • Prioritize bug detection, regression risk assessment, and missing link discovery.
  • Apply across the full stack from view to database mappings, ensuring permissions, multi-tenancy, i18n, and audit trails are considered.
  • Use Case: When reviewing a PR, automatically surface critical defects and gaps before merging.

Quick Start

Provide a code change description or PR link and ask the assistant to start a structured review focused on bugs, regressions, and missing links.

Frequently Asked Questions about forgex-review

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

FAQPage Schema
How do I automate code reviews to spot bugs and regression risks in PRs?

Automated code review identifies defects, regression risks, and missing links in code changes. Provide a code change description or PR link to trigger a structured review that surfaces critical omissions before merging.

What is cross-stack code review analysis and how does it work for full stack changes?

Cross-stack code review analysis traces logic from view through API, controller, validator, service, mapper, to SQL and config. It enforces full path verification to detect missing links and omissions across frontend and backend code layers.

How do I review multi-tenancy, permissions, and i18n logic during code changes?

Review multi-tenancy, permissions, i18n, dictionaries, and audit logs by applying cross-stack analysis to code changes. This enforces verification of security boundaries and localization rules from view components down to database mappings.

Can I use automated bug detection for debugging sessions and user-initiated code reviews?

Automated bug detection applies to PR reviews, debugging sessions, and user-initiated code review tasks. It prioritizes defect discovery, regression risk assessment, and missing link discovery across Forgex frontend and backend code.

How do I find missing links and omissions across API, controller, and service layers?

Finding missing links requires cross-stack analysis from view through API, controller, validator, service, mapper, to SQL and config. It enforces path verification to surface link gaps and logic omissions during code reviews.

What is the best way to triage code quality and regression risk in pull requests?

Triage code quality and regression risk by initiating a structured review focused on bug detection and missing link discovery. This approach prioritizes real issues like defects, link gaps, and omissions before merging code changes.