code-review

Analyze pull request diffs against the development branch to identify type safety and runtime errors.

11|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/KSD-CO/IronCode --skill code-review-ksd-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/KSD-CO/IronCode/tree/main/.ironcode/skill/code-review
Command: npx skills add https://github.com/KSD-CO/IronCode --skill code-review-ksd-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PRs often pass CI but still ship production bugs. This Skill analyzes diffs against the dev branch, checks for type safety gaps, runtime errors, and structural issues, and provides actionable findings to guide merges.

Core Features & Use Cases

  • Two-pass review workflow: distinguishes blocking issues from advisory suggestions.
  • Context-aware analysis: reads surrounding diff context and uses bun run typecheck to surface type errors.
  • Production-safety guidance: highlights potential production pitfalls (null checks, error handling, concurrency hazards) before merging.
  • Operational guidance: outputs concrete steps to fix issues and improve code quality before CI runs in upstream pipelines.

Quick Start

Run the /review workflow on your PR branch to generate a prioritized set of findings you can act on before merging.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I catch production bugs in pull requests that pass CI?

Pre-landing PR review identifies production bugs by analyzing diffs against the dev branch, checking for type safety gaps, runtime errors, and structural issues. It runs a two-pass workflow with context gathering to provide actionable findings before merging.

How does diff analysis detect type safety and runtime errors before merge?

Diff analysis reads surrounding context and runs bun run typecheck to surface type safety gaps and runtime errors. It distinguishes blocking issues from advisory suggestions, highlighting production pitfalls like null checks and concurrency hazards before merge.

Do I need bun run typecheck and git diff outputs to review PRs?

Yes, PR review requires access to git diff outputs and running bun run typecheck. These inputs provide the development branch comparison data and type validation context needed to surface CI-silent issues before merging.

What is the best way to review monorepo pull requests for CI-silent issues?

The best way to review monorepo PRs for CI-silent issues is a two-pass diff analysis against the dev branch. This distinguishes blocking issues from advisory suggestions and outputs concrete operational steps to fix type safety and runtime errors.

Can I use this PR review workflow across monorepos?

Yes, this pre-landing PR review workflow applies across monorepos. It analyzes diffs against the development branch to identify type safety gaps, runtime errors, and structural issues specific to large-scale repository architectures.

Why does CI pass but my pull request still has production safety issues?

CI passes but production safety issues remain because CI often misses runtime errors, null checks, and concurrency hazards. A two-pass diff analysis against the dev branch surfaces these CI-silent issues and provides reproducible guidance to fix them.