marmite-development

To contribute to a Rust static site generator codebase, follow standardized guidelines for safe Rust practices, mandatory test coverage, documentation updates, and pull request workflows to maintain project consistency. This Skill provides the exact checklists required.

Open source Rust code contributions require mandatory test coverage, including unit and integration tests for all code updates, new feature implementations, and bug fixes. This Skill enforces these testing requirements to maintain project consistency.

To ensure Rust code changes pass clippy and formatting checks, apply pre-defined commands for linting and formatting, explicit rules for error handling, and naming conventions. This Skill outlines the exact commands and safe Rust practices required.

Yes, you must update documentation when adding new features to a Rust project. This Skill enforces complete documentation requirements, synchronizes template updates, and ensures backward compatibility for all code changes and feature implementations.

The best way to submit a pull request for a marmite bug fix is to follow step-by-step contribution checklists, ensuring your code includes mandatory tests, passes all lint checks, and updates relevant reference documentation. This Skill provides the required workflow.

You should not use automated workflows for open source code contributions when your changes bypass architecture compliance, lack mandatory test coverage, or break backward compatibility. This Skill enforces strict guidelines to prevent missing required steps.