jc-gates

Run automated quality gates and security scans on code repositories.

Updated Feb 3, 2026

Search Tags:#code quality #automation #testing #ci/cd #security #gitleaks

Ready to run

npx skills add https://github.com/jimCresswell/jimcresswell.net --skill jc-gates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jc-gates
Source: https://github.com/jimCresswell/jimcresswell.net/tree/main/.agents/skills/jc-gates
Command: npx skills add https://github.com/jimCresswell/jimcresswell.net --skill jc-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for consistent code quality and security by automating the execution of predefined quality gates. It ensures that the codebase adheres to established standards and is free from common vulnerabilities.

Core Features & Use Cases

Automated Quality Checks: Runs a suite of tests and linters to verify code quality.
Security Scanning: Integrates tools like Gitleaks to detect secrets in the repository history.
Iterative Improvement: Facilitates a disciplined approach to fixing issues by restarting the gate sequence after each fix until all gates pass.
Use Case: A developer can use this Skill to automatically check their code against project standards before committing, ensuring a clean and secure codebase.

Quick Start

Use jc-gates to run the repo's quality gates and fix issues until all gates pass.

Frequently Asked Questions about jc-gates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate code quality checks and security scans before merging code?▼

Automated quality gates and security scans enforce coding standards by running linters, type checks, and secret scanning before code merges. This skill executes that suite of tests to verify code quality and detect vulnerabilities.

How does secret scanning work with Gitleaks in a continuous integration workflow?▼

Secret scanning with Gitleaks detects hardcoded secrets in your repository history during continuous integration. The automated quality gate scans the codebase to ensure it is free from common vulnerabilities before merging.

What is the best way to ensure my codebase adheres to established coding standards automatically?▼

Automated quality gates ensure a codebase adheres to established standards by running predefined linting and type checking checks. This automation provides consistent code quality verification for continuous integration workflows.

Can I use automated quality gates to iteratively fix linting and type checking issues?▼

Automated quality gates facilitate iterative improvement by restarting the gate sequence after each fix. This disciplined approach ensures all linting, type checking, and security scans pass before code is merged.

Do I need continuous integration setup to run automated security scans on my repository?▼

Automated security scans are designed for software development workflows requiring continuous integration. You need a code repository with established standards to run the predefined quality gates and secret scanning checks.