Evaluate changed files in a diff with QA and lead-engineer review.
npx skills add https://github.com/korchasa/foxcode --skill flowai-review
Please help me install this Agent Skill. Skill: flowai-review Source: https://github.com/korchasa/foxcode/tree/main/.claude/skills/flowai-review Command: npx skills add https://github.com/korchasa/foxcode --skill flowai-review
This Skill enables teams to conduct a combined QA and lead-engineer review focused solely on the current changes, ensuring both task completion and architectural integrity before merging.
Run the flowai-review on the current diff to perform a combined QA and lead-engineer review of changed files.
High-intent search queries and answers about installing and using this skill.
To automate a combined QA and code review for your git diff, you can run a dual-role assessment that evaluates only changed files for quality validation and architectural integrity. This diff-scoped verification ensures task completion while preventing regressions in existing functionality.
Diff-scoped verification is the process of evaluating only the changed files in a patch update rather than the entire codebase. You need it when a small feature requires both quality validation and architectural review to ensure gatekeeping and compliance before merging.
Yes, you can perform a lead-engineer architectural review alongside QA testing simultaneously. This combined review approach evaluates current changes from both design and quality perspectives, ensuring architectural integrity and task completion before merging.
To ensure code review compliance and link the report to a task workflow, apply a dual-role assessment to your changed files. The review outcome is captured in a structured report and linked directly to the task management workflow for remediation tracking.
The best way to review small patches for quality and architecture is to run a dual-role QA and lead-engineer assessment focused solely on the current diff. This ensures adherence to project conventions and signals issues for remediation when needed.
This review process checks only the new changes by assessing the diffs to prevent regression on existing functionality. It does not evaluate the entire codebase, focusing solely on the current patch or feature update to ensure both quality and design integrity.
ceejbotReview Rust diffs with evidence-cited findings and ranked fixes.
matteocervelliAssess software vulnerabilities with CVSS scoring and remediation planning.
skkeoriwExecute pre-commit code review with static analysis and automated tests.
robertzengcnAggregate code quality metrics from multiple tools into a weighted 0-10 composite score.
