
Rule Auditor
- 54 installs
- 36 repo stars
- Updated July 14, 2026
- oimiragieo/agent-studio
Helps with security tasks.
About
rule-auditor is a Claude Code skill for security. It helps solo builders move faster with AI-assisted development.
- rule-auditor
- Security
- AI-coding skill
Rule Auditor by the numbers
- 54 all-time installs (skills.sh)
- Ranked #1,278 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill rule-auditorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 54 |
|---|---|
| repo stars | ★ 36 |
| Last updated | July 14, 2026 |
| Repository | oimiragieo/agent-studio ↗ |
What it does
Helps with security tasks.
Files
Rule Auditor Skill
<identity> Rule Auditor - Validates code against coding standards and best practices from expert skills. Reports compliance violations and suggests fixes. </identity>
<capabilities>
- Auditing code against best practices
- Identifying violations and anti-patterns
- Suggesting fixes for violations
- Generating compliance reports
</capabilities>
<instructions> <execution_process>
Step 1: Identify Applicable Skills
Find relevant expert skills based on the code being audited:
| File Type | Expert Skills |
|---|---|
.ts, .tsx | typescript-expert, react-expert |
.py | python-backend-expert |
.go | go-expert |
.java | java-expert |
*.test.* | testing-expert |
Step 2: Load Best Practices
Read the relevant skill files to understand best practices:
cat .claude/skills/[skill-name]/SKILL.mdExtract key rules and patterns to check for.
Step 3: Scan Target Files
Analyze the target files for violations:
1. Read target files: Use Read tool to examine code 2. Check patterns: Look for anti-patterns from skill guidelines 3. Identify issues: Note file, line, and violation type
Common checks:
- Naming conventions
- Code structure
- Import patterns
- Type safety
- Security issues
- Performance anti-patterns
Step 4: Generate Report
Create a structured compliance report:
## Audit Report
**Target**: src/components/
**Skills Applied**: react-expert, typescript-expert
**Date**: YYYY-MM-DD
### Summary
- **Pass**: 12 rules
- **Warn**: 3 rules
- **Fail**: 2 rules
### Violations
#### FAIL: Avoid using `any` type
- **File**: src/components/UserAuth.tsx:45
- **Issue**: `const user: any = await getUser()`
- **Fix**: Define proper User interface
#### WARN: Use Server Components by default
- **File**: src/components/UserAuth.tsx:1
- **Issue**: Missing 'use client' directive but uses useState
- **Fix**: Add 'use client' or refactor to Server Component</execution_process>
<best_practices>
1. Run Early: Audit during development, not just before commit 2. Prioritize: Focus on high-severity violations first 3. Be Specific: Include file paths and line numbers 4. Suggest Fixes: Provide actionable remediation steps 5. Group Issues: Organize by severity and category
</best_practices> </instructions>
<examples> <usage_example> Audit Request:
Audit src/components/ for TypeScript and React best practicesResponse:
## Audit Report: src/components/
### Violations Found
1. **[ERROR]** src/components/User.tsx:23
- Rule: Avoid `any` type
- Code: `const data: any = response.json()`
- Fix: `const data: UserResponse = response.json()`
2. **[WARN]** src/components/Form.tsx:1
- Rule: Prefer Server Components
- Issue: Uses useState without 'use client'
- Fix: Add 'use client' directive at top
### Passed Checks
- Component naming (PascalCase) ✓
- Hook usage patterns ✓
- Import organization ✓</usage_example> </examples>
Rules
- Always check relevant expert skills for standards
- Provide line numbers and specific fixes
- Prioritize security and type safety issues
Memory Protocol (MANDATORY)
Before starting:
cat .claude/context/memory/learnings.mdAfter completing:
- New pattern ->
.claude/context/memory/learnings.md - Issue found ->
.claude/context/memory/issues.md - Decision made ->
.claude/context/memory/decisions.md
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
Invoke the rule-auditor skill and follow it exactly as presented to you
'use strict';
/**
* Post-execute hook for rule-auditor
* Auto-generated by enterprise-bundle-scaffolder
*
* Records metrics after skill execution.
*/
function postExecute(_context) {
// Record execution metrics
return { ok: true, skill: 'rule-auditor' };
}
module.exports = { postExecute };
'use strict';
/**
* Pre-execute hook for rule-auditor
* Auto-generated by enterprise-bundle-scaffolder
*
* Validates inputs before skill execution.
*/
function preExecute(context) {
// Validate skill invocation context
if (!context || typeof context !== 'object') {
return { allow: true, message: 'rule-auditor: no context to validate' };
}
return { allow: true };
}
module.exports = { preExecute };
rule-auditor Research Requirements
Generated: 2026-02-28
Skill Description
Validates code against coding standards and best practices. Reports compliance violations and suggests fixes.
Research Areas
- Current best practices for rule-auditor
- Industry standards and tooling
- Integration patterns
Source References
- To be populated by skill-updater research phase
rule-auditor Rules
Purpose
Validates code against coding standards and best practices. Reports compliance violations and suggests fixes.
Best Practices
- Run audits early in development cycle
- Focus on high-severity violations first
- Provide specific, actionable fixes
- Group violations by category
Integration Points
See SKILL.md for complete documentation.
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "rule-auditorInput",
"description": "Input schema for Validates code against coding standards and best practices. Reports compliance violations and suggests fixes.",
"type": "object",
"additionalProperties": true,
"properties": {
"target": {
"type": "string",
"description": "Target file or path for the skill to operate on"
},
"options": {
"type": "object",
"description": "Additional options for skill execution",
"additionalProperties": true
}
}
}
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "rule-auditorOutput",
"type": "object",
"additionalProperties": true,
"properties": {
"ok": {
"type": "boolean"
},
"summary": {
"type": "string"
}
}
}
#!/usr/bin/env node
'use strict';
/**
* rule-auditor - Enterprise Skill Script
* Auto-generated by enterprise-bundle-scaffolder
*/
const fs = require('fs');
const path = require('path');
// Parse arguments
const args = process.argv.slice(2);
const options = {};
for (let i = 0; i < args.length; i++) {
if (args[i].startsWith('--')) {
const key = args[i].slice(2);
const value = args[i + 1] && !args[i + 1].startsWith('--') ? args[++i] : true;
options[key] = value;
}
}
if (options.help) {
console.log(`
rule-auditor - Enterprise Skill
Usage:
node main.cjs --check <file> Check a file against guidelines
node main.cjs --list List all guidelines
node main.cjs --help Show this help
Description:
Validates code against coding standards and best practices. Reports compliance violations and suggests fixes.
`);
process.exit(0);
}
if (options.list) {
console.log('Guidelines for rule-auditor:');
console.log('See SKILL.md for full guidelines');
process.exit(0);
}
console.log('rule-auditor skill loaded. Use with Claude for code review.');
rule-auditor Implementation Template
Goal
- Define target outcome and acceptance criteria.
TDD
1. Red 2. Green 3. Refactor
Verification
- lint
- format
- targeted tests