Guardian Skill

Validate commits and release readiness with linters, tests, builds, and CI/CD simulations.

4|1|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/deMGoncalves/arq-specs-template --skill guardian-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Guardian Skill
Source: https://github.com/deMGoncalves/arq-specs-template/tree/main/.claude/skills/guardian
Command: npx skills add https://github.com/deMGoncalves/arq-specs-template --skill guardian-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken builds, failed tests, and linter errors from reaching your remote repository or CI/CD pipeline. It automates comprehensive quality checks before commit, push, or release, saving time and resources by catching issues early.

Core Features & Use Cases

  • Pre-Commit/Push Validation: Automatically runs linters, tests, and builds, and even simulates CI/CD workflows locally to ensure everything passes before interacting with Git.
  • Release Management: Validates SemVer versioning, CHANGELOG.md updates, and prepares release tags and notes, streamlining the release process.
  • Security & Compliance: Checks for critical vulnerabilities, sensitive files (.env, secrets), and enforces Conventional Commits, enhancing project security and maintainability.
  • Use Case: Before pushing your latest feature, invoke the Guardian to perform a full suite of checks. It will ensure all tests pass, linters are clean, and the build is successful, giving you confidence that your changes won't break the main branch or fail CI.

Quick Start

To validate your changes and commit them securely: @skill guardian To validate, commit, and push: @skill guardian push

Frequently Asked Questions about Guardian Skill

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

FAQPage Schema
How do I prevent broken code from reaching my repository?

Pre-commit validation catches linters, tests, build failures, and security issues before push. Guardian automates these checks locally, blocking commits that fail and saving CI/CD resources by stopping problems at the source.

Can I automate release management with version checks and changelog updates?

Yes. Guardian validates SemVer versioning, ensures CHANGELOG.md is updated, generates Conventional Commits messages, and prepares release tags and notes—streamlining the entire release workflow without manual steps.

How do I detect sensitive files and enforce security compliance before pushing?

Guardian scans for critical vulnerabilities, detects sensitive artifacts like .env files and secrets, and enforces Conventional Commits standards. It blocks push operations on security failures, preventing credential leaks and compliance violations.

Does pre-commit validation work across multiple programming languages?

Yes. Guardian applies across multi-language codebases, running language-agnostic checks like linters, tests, builds, and CI/CD simulations. It adapts to your project's tech stack without requiring language-specific configuration.

What happens during a dry-run validation workflow?

Dry-run mode executes all checks—linters, tests, builds, security scans, version validation, and changelog verification—without committing or pushing. Guardian generates comprehensive reports so you can review results before acting.

Can Guardian simulate CI/CD pipeline behavior locally before pushing?

Yes. Guardian simulates your CI/CD workflows locally during pre-commit and push stages, catching integration failures before they reach the remote pipeline and reducing feedback-loop time.