mojo-format

Format Mojo code files to enforce consistent style and indentation.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill mojo-format-homericintelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mojo-format
Source: https://github.com/HomericIntelligence/ProjectOdyssey/tree/main/.claude/skills/mojo-format
Command: npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill mojo-format-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures consistent code style and formatting for Mojo files, making codebases cleaner and easier to maintain.

Core Features & Use Cases

  • Code Formatting: Applies standard Mojo formatting rules to your code.
  • Pre-commit Hook Integration: Can be used to automatically format code before commits.
  • Use Case: Before committing a new feature, run this Skill to ensure all your Mojo code adheres to the project's style guide.

Quick Start

Use the mojo-format skill to format the file at path/to/file.mojo.

Frequently Asked Questions about mojo-format

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

FAQPage Schema
How do I format Mojo code files to enforce consistent style?

You can format Mojo code by applying standard formatting rules to individual files or entire directories, ensuring consistent indentation and style across your project.

Can I run a Mojo code formatter on an entire project directory?

Yes, you can apply Mojo formatting to entire directories within a project, automatically enforcing consistent indentation and style rules across all included files.

How do I automate code style enforcement before committing Mojo files?

You can automate code style enforcement by integrating the formatter as a pre-commit hook, ensuring all Mojo files adhere to your style guide before changes are committed to version control.

Why do I need to format Mojo code before version control?

Formatting Mojo code before version control ensures automated style enforcement, resulting in a cleaner codebase that is easier to maintain and review during collaborative development.

Does Mojo formatting work with pre-commit hooks?

Yes, Mojo formatting supports pre-commit hook integration, allowing you to automatically apply standard style rules to your code before changes are committed to version control.