lint

Enforce coding standards for Rust, TOML, and Markdown files using dprint and clippy.

106|5|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Firma-AI/openfirma --skill lint-firma-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/Firma-AI/openfirma/tree/main/.skills/lint
Command: npx skills add https://github.com/Firma-AI/openfirma --skill lint-firma-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps maintain code quality in OpenFirma by enforcing formatting and linting rules.

Core Features & Use Cases

  • Automated Code Formatting: Ensures consistent coding style and formatting for Rust, TOML, and Markdown.
  • Linting: Detects and reports on common coding issues.
  • Use Case: Before pushing code changes, this Skill can be run to verify that your code adheres to OpenFirma's coding standards.

Quick Start

Run 'lint' to check formatting and lint rules for your OpenFirma code changes.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I automate Rust code formatting and linting for continuous integration?

Automate Rust code formatting and linting by running a single command that enforces consistent coding style and checks for common issues using dprint and clippy. This verifies that code changes adhere to project standards before integration.

Can I lint TOML and Markdown files alongside Rust in OpenFirma projects?

Yes, you can lint TOML and Markdown files alongside Rust code. The Skill enforces formatting rules and consistent coding style across all three file types for OpenFirma projects using dprint and clippy.

What's the best way to enforce coding standards before pushing code changes?

The best way to enforce coding standards is to run a single lint command before pushing. It checks formatting consistency and lints common issues in Rust, TOML, and Markdown files to ensure adherence to project standards.

Does this code linting tool require any specific dependencies to run?

No specific dependencies are required to run this code linting tool. It operates as a standalone script component that executes dprint and clippy to check formatting and lint rules for OpenFirma code changes.

Why does my code formatting check fail during continuous integration?

Code formatting checks fail during continuous integration when files do not adhere to consistent coding style rules. The linter detects and reports these common coding issues in Rust, TOML, and Markdown files before changes are pushed.

When do I need to run code linting in my software development workflow?

You need to run code linting before pushing code changes to verify adherence to OpenFirma's coding standards. It is specifically designed for continuous integration workflows in software development to maintain consistent formatting and detect common issues.