Markdown Converter
Agent skill for markdown-converter
Universal guidelines for AI agents and developers. This file is used verbatim across multiple projects.
Sign in to like and favorite skills
Universal guidelines for AI agents and developers. This file is used verbatim across multiple projects.
main or masterfeature/add-login, fix/memory-leak)gh pr create --title "Your title" --body "Description" to open PRsFollow Conventional Commits:
<type>[optional scope]: <description>
Types:
feat, fix, docs, style, refactor, perf, test, build, ci, chore
Examples:
feat: add user authentication fix(auth): resolve null pointer in login docs: update installation guide
Pinning dependencies is vital for reproducible builds and reducing bit rot.
Examples:
rust-toolchain.tomlubuntu-24.04 instead of ubuntu-latest)cargo-audit)package-lock.json, Cargo.lock)Enforced linting vastly improves the quality, readability, and conformity of code. Linters should always be used and strictly enforced in CI. If a language has tooling for static analysis, it should be used.
Examples:
shellcheck for shell scriptsstatix for Nix filescargo clippy for Rust fileshlint for Haskell filesmarkdownlint for Markdown filesyamllint for YAML filesactionlint for GitHub Actions workflow filescommitlint for commit messagesConsistent code formatting improves readability and reduces friction during code reviews. Formatters should be enforced in CI alongside linters.
Examples:
alejandra for Nix filesrustfmt for Rust filesleptosfmt for Leptos view! macrosprettier for JavaScript/TypeScript/JSON/Markdown filesshfmt for shell scriptscargo audit) with pinned CVE databases that auto-update at least monthly.