Orchestrate parallel agent-based code review and static analysis across multiple languages.
npx skills add https://github.com/kok1eee/o-m-cc --skill quality-gate-kok1eee
Please help me install this Agent Skill. Skill: quality-gate Source: https://github.com/kok1eee/o-m-cc/tree/main/skills/quality-gate Command: npx skills add https://github.com/kok1eee/o-m-cc --skill quality-gate-kok1eee
This Skill performs end-to-end pre-merge validation by orchestrating parallel human-like reviewers and language-specific static analysis to catch critical bugs, security issues, and plan drift before code is merged.
Run the quality-gate skill with a specific file path or with 'all' to spawn the review council, aggregate findings, and run linters.
High-intent search queries and answers about installing and using this skill.
Automated pre-merge validation uses parallel agent-based code review and static analysis to catch critical bugs and security issues before merging. It orchestrates multiple reviewer agents and language-specific linters to independently evaluate diffs and cross-verify findings.
Automated lint checks support Python, TypeScript, Shell, Rust, and Go by streaming linters in parallel. It runs tools like ruff, shellcheck, tsc, and clippy with fallbacks when specific tools are unavailable on the system.
Spawning a parallel review council is the best way to surface security-critical problems before a PR. It deploys independent security-reviewer and critic agents to evaluate diffs, cross-verify findings, and aggregate reports for immediate visibility.
Automated code review works without specific linting tools installed by using built-in tool presence fallbacks. The monitor-driven linting process detects missing tools and automatically adjusts its static analysis approach to continue providing validation.
An automated remediation loop fixes critical issues during pre-merge validation by attempting machine-led fixes and re-running the review. This cycle repeats until all critical issues are resolved or user intervention is required.
You should not use an automated agent team for code review when manual architectural decisions or highly subjective design critiques are required. It is designed for static analysis, security validation, and plan drift detection rather than nuanced human judgment.
umairinayatLint, format, and statically analyze Node.js and Python code changes.
openshift-engTriage CodeRabbit review comments on GitHub pull requests into actionable categories.
motlinRun precommit checks on code changes and report failures.
rysweetOrchestrate a six-phase parallel codebase quality audit with GitHub issues and PRs.
