standardize

Generate project-specific coding guidelines from source repositories into ai/context/coding_guidelines.md.

10|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/fiftynotai/igris-ai --skill standardize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standardize
Source: https://github.com/fiftynotai/igris-ai/tree/main/.claude/skills/standardize
Command: npx skills add https://github.com/fiftynotai/igris-ai --skill standardize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a clear, project-specific coding_guidelines.md so teams have consistent architecture decisions, naming conventions, testing expectations, and review checklists without manually auditing the entire codebase.

Core Features & Use Cases

  • Four operational modes: extract standards from a base architecture, analyze an existing project, merge base + project patterns with conflict resolution, or produce minimal platform best-practices for new projects.
  • Automated analysis: scans file structure, detects platform/framework, infers naming and architectural patterns, and documents examples and overrides.
  • Safe output-only workflow: writes ai/context/coding_guidelines.md and never modifies source files while documenting the chosen mode and providing concrete examples and commit/PR conventions.
  • Use case: standardize conventions across a mono-repo by merging an organizational base repo with project-specific deviations, producing a single authoritative guideline file.

Quick Start

Generate coding guidelines for this repository using analyze mode and save the output to ai/context/coding_guidelines.md.

Frequently Asked Questions about standardize

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

FAQPage Schema
How do I generate coding guidelines from an existing repository?

Generate coding guidelines from an existing repository by scanning the source code to detect platforms, infer architectural patterns, and extract naming conventions into a coding_guidelines.md file. This automated analysis produces consistent project-specific standards without manual auditing.

What is the best way to standardize coding standards across a mono-repo?

Standardize coding standards across a mono-repo by merging an organizational base architecture with project-specific deviations. This conflict resolution process produces a single authoritative coding guidelines file ensuring consistent conventions and review checklists across all nested projects.

Can I extract coding standards from a base architecture for new projects?

Yes, you can extract coding standards from a base architecture or produce minimal platform best-practices for new projects. This generates foundational coding guidelines documenting architectural decisions and naming conventions before any project-specific code is written.

Does generating project-specific coding guidelines modify my source files?

Generating project-specific coding guidelines does not modify source files. The workflow operates under a strict output-only constraint, safely writing the extracted standards and architectural patterns exclusively to ai/context/coding_guidelines.md.

What should coding guidelines include for consistent architecture decisions?

Coding guidelines should include platform detection, concrete code examples, naming conventions, testing expectations, commit and PR conventions, and review checklists. Documenting these elements ensures teams maintain consistent architecture decisions without manually auditing the codebase.