repo-source-code-review

Reviews PRs and source code changes in Git repositories for compliance with packaging and framework conventions.

1.1k|32|Updated Apr 5, 2025

Search Tags:#documentation #review #code-quality #naming-conventions #pull-requests #tests #purity-annotation

Ready to run

npx skills add https://github.com/open-circle/formisch --skill repo-source-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-source-code-review
Source: https://github.com/open-circle/formisch/tree/main/skills/repo-source-code-review
Command: npx skills add https://github.com/open-circle/formisch --skill repo-source-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams review PRs and source code changes across Formisch packages and frameworks to ensure consistency, quality, and adherence to project standards.

Core Features & Use Cases

Guided PR review: Verify naming conventions, purity annotations, types, docs, and tests across packages.
Pattern validation: Ensure code follows established conventions like FormStore, useField, createForm.
Pre-merge quality gate: Serve as a checklist for merges to prevent regressions.

Quick Start

Use the repo-source-code-review skill to evaluate a PR by applying the review guide to changed files in packages/ and frameworks/.

Frequently Asked Questions about repo-source-code-review

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

FAQPage Schema

How do I review pull requests for naming conventions and purity annotations?▼

Review pull requests by applying a guided checklist to changed files, verifying naming conventions, purity annotations, types, docs, and tests align with project standards.

What's the best way to run a pre-merge quality gate for source code changes?▼

Run a pre-merge quality gate by evaluating source code changes against established patterns like FormStore and useField to prevent regressions and ensure consistency across packages.

How does pattern validation work for framework source code modifications?▼

Pattern validation works by checking modified files in packages and frameworks directories to ensure code follows established conventions like createForm, FormStore, and useField patterns.

Can I use this code review skill to verify test coverage and type safety across packages?▼

Yes, you can verify test coverage and type safety across packages by applying the review guide to changed files, ensuring all modifications meet project documentation and type standards.

Does the pull request review process support frameworks and packages directories?▼

Yes, the pull request review process explicitly supports evaluating changed files within both packages/ and frameworks/ directories to ensure project-wide consistency.

When do I need a guided PR review for source code changes?▼

You need a guided PR review when merging source code changes across packages and frameworks to validate naming conventions, purity annotations, type safety, documentation, and test coverage.