Releases: MarkdownLM/cli
mdlm CLI v0.2.0
The mdlm CLI v0.2.0 introduces three core governance commands: query, validate, and resolve-gap. These tools enable teams to search their knowledge base for architectural patterns, cross-check code against documented standards, and identify documentation gaps directly from the terminal. All commands are category-aware, supporting focused domains such as security, error_handling, and dependencies.
The query and validate commands provide instant feedback through integration with the MarkdownLM API.
mdlm queryretrieves documented rules and highlights missing or incomplete guidance.mdlm validateanalyzes code for policy violations and provides actionable fix suggestions aligned with established team standards.
Both commands support local file paths and inline code snippets, making them easy to integrate into existing development workflows, CI pipelines, or pre-commit hooks.
To maintain documentation integrity, mdlm resolve-gap identifies and tracks undocumented architectural decisions. It leverages team policies to infer missing rules where possible or flags gaps for manual resolution, ensuring the knowledge base evolves alongside the codebase.
MarkdownLM CLI v0.1.0
The initial open-source release of the mdlm CLI introduces a powerful, Git-inspired workflow for managing your architectural knowledge base from the terminal. Developers can now use familiar commands such as clone, pull, and push to synchronize their knowledge base with the MarkdownLM. This release focuses on developer ergonomics, providing a manifest-based tracking system that identifies local changes and ensures that your team's documented truths are always accessible, even when working offline. Security and precision are at the core of this first iteration, featuring a configure command that handles API keys with strict file permissions to protect your workspace. The CLI's ability to track document state locally allows teams to treat their knowledge base and prevent conflicting edits. This version sets the foundation for a robust "docs-as-code" ecosystem where architectural governance is as easy to manage as a source code repository.