cncf-pre-commit

Run cargo fmt, clippy, and tests for MCPAtlas pre-commit quality gates.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/aryasoni98/mcpatlas --skill cncf-pre-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cncf-pre-commit
Source: https://github.com/aryasoni98/mcpatlas/tree/main/.cursor/skills/cncf-pre-commit
Command: npx skills add https://github.com/aryasoni98/mcpatlas --skill cncf-pre-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of running essential quality checks and formatting code before committing changes, ensuring consistency and preventing common errors in the MCPAtlas repository.

Core Features & Use Cases

  • Automated Quality Gates: Runs cargo fmt, clippy, and tests to maintain code standards.
  • Conventional Commits: Helps generate well-formatted commit messages.
  • Pre-Commit Checks: Scans for common issues like unwrap(), dbg!, println!, secrets, and TODOs.
  • Use Case: Before pushing a new feature, use this Skill to automatically format your code, check for lints and bugs, and create a standardized commit message, saving review time and improving code health.

Quick Start

Run the cncf-pre-commit skill to format, lint, and test the code before committing.

Frequently Asked Questions about cncf-pre-commit

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

FAQPage Schema
How do I automate Rust code formatting and linting before a git commit?

This Skill automates pre-commit quality gates for Rust by running cargo fmt and clippy. It formats code and scans staged changes to enforce standards before committing.

How do I enforce conventional commit messages in a Rust project?

To enforce conventional commit messages in a Rust project, this Skill validates your commit message structure during the pre-commit phase. It ensures your commits follow standardized formatting rules.

How do I scan staged changes for security vulnerabilities and anti-patterns?

Scanning staged changes for security vulnerabilities and anti-patterns is handled by the pre-commit checks in this Skill. It detects common Rust issues like unwrap(), dbg!, println!, secrets, and TODOs.

Can I run cargo tests automatically as part of my git hooks?

Yes, you can run cargo tests automatically as part of your git hooks. This Skill integrates testing into its pre-commit quality gates, ensuring your Rust code passes tests before committing.

What is the best way to prevent unwrap() and dbg! macros from being committed?

The best way to prevent unwrap() and dbg! macros from being committed is using automated pre-commit scans. This Skill blocks these common Rust anti-patterns by scanning staged changes before commit.