code-editing

Enforce Rust coding conventions and testing workflows in the mdvs codebase.

27|2|Updated Feb 22, 2026

Search Tags:#workflow #testing #rust #code-review #code-editing #code-conventions #mdvs

Ready to run

npx skills add https://github.com/edochi/mdvs --skill code-editing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-editing
Source: https://github.com/edochi/mdvs/tree/main/.claude/skills/code-editing
Command: npx skills add https://github.com/edochi/mdvs --skill code-editing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and enforces coding conventions for Rust changes in the mdvs codebase, ensuring consistent implementation, testing, and downstream updates.

Core Features & Use Cases

Code Editing Conventions: Guidelines for reading existing code, matching style, and planning changes with stakeholders.
Testing & Verification: Recommendations to run unit tests, integration tests, clippy, and fmt to maintain quality, and to verify end-to-end behavior across example_kb and docs.
Workflow & Documentation Updates: Instructions for updating specs, example_kb, and mdbook when changing the code or APIs.

Quick Start

Follow the Code Editing Conventions when modifying mdvs Rust code, then run cargo test, cargo clippy, and cargo fmt to verify changes.

Frequently Asked Questions about code-editing

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

FAQPage Schema

What are the standard conventions for editing Rust code in the mdvs codebase?▼

Rust code editing conventions in mdvs require reading existing code, matching established style, and planning changes with stakeholders to ensure uniform development practices across the codebase.

How do I verify Rust code changes in mdvs after implementation?▼

Verify Rust code changes by running cargo test for unit and integration tests, cargo clippy for linting, and cargo fmt to ensure formatting compliance before completing the workflow.

What documentation needs updating when modifying Rust APIs in mdvs?▼

When changing Rust code or APIs in mdvs, you must update specs, example_kb, and mdbook to maintain accurate downstream documentation and ensure end-to-end validation across the project.

Does the mdvs code-editing workflow support end-to-end validation with standard Rust tooling?▼

Yes, the mdvs code-editing workflow enforces end-to-end validation using standard Rust tooling including cargo test, cargo clippy, and cargo fmt to verify behavior across example_kb and docs.

Why should I follow code editing conventions when making Rust changes to mdvs?▼

Following code editing conventions standardizes implementation, testing, and downstream updates for Rust changes in mdvs, ensuring consistent quality and uniform development practices across the entire codebase.

What testing requirements must I meet when modifying Rust code in mdvs?▼

Rust code modifications in mdvs require running unit tests, integration tests, clippy linting, and fmt formatting to maintain quality and verify end-to-end behavior across example_kb and documentation.