Run any Skill in Manus with one click

code-quality-gate

Stars9

Forks0

UpdatedMay 15, 2026 at 01:57

Run all code quality checks (security, complexity, test coverage) on the current PR and post a combined report as a GitHub PR comment. Use before merging a PR, during code review, or when asked to check code quality.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

davila7

davila7/claude-with-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

title	code-quality-gate
name	code-quality-gate
description	Run all code quality checks (security, complexity, test coverage) on the current PR and post a combined report as a GitHub PR comment. Use before merging a PR, during code review, or when asked to check code quality.
disable-model-invocation	true
allowed-tools	Bash(gh pr *)

Run the complete code quality gate for this PR.

Pre-flight

Check whether an open PR exists: !gh pr view --json number,title,headRefName 2>/dev/null || echo "NO_PR"

If the output above contains "NO_PR", note that no PR is open. Proceed with the scans anyway, but print the final report to the terminal instead of posting it as a comment.

Steps

Run /security-scan. It will return findings in this format:
```
SECURITY FINDINGS:
- [severity] file:line — description
```
Capture the full output.
Run /complexity-check. It will return findings in this format:
```
COMPLEXITY FINDINGS:
- file:line — description
```
Capture the full output.
Run /test-coverage-check. It will return findings in this format:
```
COVERAGE FINDINGS:
- source-file — description
```
Capture the full output.
Collect all three findings blocks.
If a PR is open, invoke @quality-reporter with this message: "Post a code quality report for this PR with the following findings. Format as a GitHub PR comment and post it.

[paste the SECURITY FINDINGS block here]

[paste the COMPLEXITY FINDINGS block here]

[paste the COVERAGE FINDINGS block here]"

Confirm the comment URL was returned and print it.
If no PR is open, format and print the report to the terminal using the same structure the quality-reporter would use.

Summary line

After posting (or printing), output a summary: "Code quality gate complete. Security: [count or 'clean'], Complexity: [count or 'clean'], Coverage: [count or 'clean']."

More from this repository

same repository

explain-code

davila7/claude-with-skills

Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".

2026-05-159

summarize-changes-headless

davila7/claude-with-skills

Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.

2026-05-159

hello-skill

davila7/claude-with-skills

Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.

2026-05-159

personal-greeting

davila7/claude-with-skills

Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.

2026-05-159

project-conventions

davila7/claude-with-skills

Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.

2026-05-159

changelog-entry

davila7/claude-with-skills

Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.

2026-05-159

title	code-quality-gate
name	code-quality-gate
description	Run all code quality checks (security, complexity, test coverage) on the current PR and post a combined report as a GitHub PR comment. Use before merging a PR, during code review, or when asked to check code quality.
disable-model-invocation	true
allowed-tools	Bash(gh pr *)

Run the complete code quality gate for this PR.

Pre-flight

Check whether an open PR exists: !gh pr view --json number,title,headRefName 2>/dev/null || echo "NO_PR"

If the output above contains "NO_PR", note that no PR is open. Proceed with the scans anyway, but print the final report to the terminal instead of posting it as a comment.

Steps

Run /security-scan. It will return findings in this format:
```
SECURITY FINDINGS:
- [severity] file:line — description
```
Capture the full output.
Run /complexity-check. It will return findings in this format:
```
COMPLEXITY FINDINGS:
- file:line — description
```
Capture the full output.
Run /test-coverage-check. It will return findings in this format:
```
COVERAGE FINDINGS:
- source-file — description
```
Capture the full output.
Collect all three findings blocks.
If a PR is open, invoke @quality-reporter with this message: "Post a code quality report for this PR with the following findings. Format as a GitHub PR comment and post it.

[paste the SECURITY FINDINGS block here]

[paste the COMPLEXITY FINDINGS block here]

[paste the COVERAGE FINDINGS block here]"

Confirm the comment URL was returned and print it.
If no PR is open, format and print the report to the terminal using the same structure the quality-reporter would use.

Summary line

After posting (or printing), output a summary: "Code quality gate complete. Security: [count or 'clean'], Complexity: [count or 'clean'], Coverage: [count or 'clean']."