adjustCodingRule

Validate source code against doc/Coding_Rule.txt and write PASS/FAIL reports.

Updated May 21, 2026
One-click install
npx skills add https://github.com/kinetas/harness_engineering --skill adjustcodingrule
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adjustCodingRule
Source: https://github.com/kinetas/harness_engineering/tree/main/adjustCodingRule
Command: npx skills add https://github.com/kinetas/harness_engineering --skill adjustcodingrule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you detect when your code violates established coding standards by automatically validating files against Coding_Rule.txt.

Core Features & Use Cases

  • Rule-based code compliance checking: Compares target source files to the requirements defined in doc/Coding_Rule.txt.
  • Scoped validation: Validates either a single file (when provided) or the entire develope/ directory (when not provided).
  • Actionable violation reporting: Produces a timestamped detailed result file and optionally triggers developer-fix guidance.

Quick Start

Run /adjustCodingRule path/to/your/file to check that file against doc/Coding_Rule.txt.

Frequently Asked Questions about adjustCodingRule

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

FAQPage Schema
How do I validate source code against organization-specific coding standards?▼

To validate code compliance against your coding rules, the Skill checks source files against the requirements defined in doc/Coding_Rule.txt and generates a timestamped PASS/FAIL report.

Can I run static code review on a single file instead of the whole project?▼

Yes, static code review supports scoped validation. You can validate a single file by providing its path as an argument, or validate the entire develope/ directory by omitting the path.

How does rule-based code compliance checking work for project maintenance?▼

Rule-based code compliance checking works by parsing the text in doc/Coding_Rule.txt, spawning a Debugger AI to evaluate your source files for violations, and writing the results to a report file.

What do I need to set up to check code compliance using a custom rules file?▼

To check code compliance, your environment must contain your custom rules defined in doc/Coding_Rule.txt and your target source files located within the develope/ directory.

What is the best way to provide developer feedback for code standard violations?▼

The best way to provide developer feedback for coding standard violations is to use the generated timestamped report file, which optionally triggers developer-fix guidance based on the detected rule violations.

Are there limitations when validating code against Coding_Rule.txt?▼

A limitation is that validation strictly requires rules to be defined in doc/Coding_Rule.txt, and full validation is scoped exclusively to the develope/ directory when no specific file path is provided.