finish

To verify tests and review code before a pull request, this Skill orchestrates a multi-stage quality gate that runs automated testing, mandates code review, and performs red-teaming before presenting merge or PR options.

The best way to automate code review and security checks before merging is using a workflow that integrates adversarial red-teaming and mandatory review sub-skills to find vulnerabilities and ensure code quality before integration.

Yes, you can choose between merging locally and creating a pull request. After tests pass and code review completes, the workflow presents structured, user-guided integration decisions for your completed development branch.

Yes, the red-teaming code review process works without external testing dependencies. The Skill relies on internal sub-skills and scripts to perform security checks and verification deterministically.

You should use a multi-stage quality gate for development workflow integration when you need robust verification, mandatory code review, and adversarial testing to find vulnerabilities before confidently completing a feature.

Steps to complete a git pull request workflow with automated testing include verifying all tests pass, executing mandatory code review, running red-teaming for vulnerabilities, and selecting a structured merge, PR, or cleanup option.