agent-tech-lead-review

Automating the final code review and merge process for pull requests requires a gatekeeper mechanism that verifies code quality against acceptance criteria and checks CI gate status. This Skill executes merges when checks pass or requests changes when issues surface.

A post-pipeline gatekeeper for production readiness is an automated final check that operates after development and testing stages complete. It verifies code changes against acceptance criteria and CI gate adherence before allowing a merge into the main branch.

Yes, this automated code review tool checks CI gate status before merging. It verifies continuous integration workflows have passed and then executes the pull request merge only if all quality checks and acceptance criteria are met.

You can use this to automatically merge a pull request only when acceptance criteria pass. It performs a final check of code changes against your defined requirements and leaves the pull request open with feedback if issues are found.

When automated code review finds issues, the pull request is left open with feedback instead of being merged. The Skill requests changes based on its findings against acceptance criteria and CI gate status, ensuring code quality is maintained.

You should not use an automated merge gatekeeper when manual oversight is required for complex changes or when acceptance criteria cannot be clearly defined. It is designed for post-pipeline production readiness after all standard development and testing stages are complete.