Add ub-rust skill for Rust development - #3
Open
Zyra-V21 wants to merge 1 commit into
Open
Conversation
New language skill following the same structure as ub-python and ub-ts: SKILL.md contract, portable standards reference with official source map, repository workflow discovery, and cargo lint-table policy resolution with a starter profile applied as a reviewed Cargo.toml edit. Registered in AGENTS.md, README, marketplace.json, the docs sidebar, and the skill catalog index. All repo maintenance checks pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a Rust language skill built on the same structure and principles as ub-python and ub-ts: repo truth first, modern patterns for new code, bounded legacy exceptions, and validation after edits.
Contents:
SKILL.mdwith the usual contract: routing description, core workflow, version and research policy with OFFICIAL_CONFLICT/UNVERIFIED disclosures, implementation rules, legacy guardrails, output requirements, and completion checklist.references/rust-standards.md: portable modern Rust baseline (edition and MSRV truth, ownership-first API design, structured errors in the thiserror/anyhow split, async and concurrency discipline, unsafe policy with SAFETY comments, lint policy via manifest[lints]tables and#[expect], testing practice) with an official source map. Nightly-only features like TAIT are explicitly kept out of the guidance.references/repository-rust-workflows.md: resolving a repo's actual toolchain, workspace, feature matrix, and validation truth before recommending commands.references/cargo-lints-resolution.md: lint policy discovery across manifest tables, clippy/rustfmt configs, and CI flags, plus starter adoption steps.assets/lints-template/Cargo-lints.toml: a starter[lints.rust]/[lints.clippy]profile. Unlike the Ruff and golangci starters, the merge target (Cargo.toml) always already exists, so this ships no scaffold script on purpose: adoption stays a reviewed manifest edit, in line with the catalog's scaffolding conventions.Validation: check_repo_catalog, check_package_metadata, check_repo_paths and check_skill_schema all pass, and check-docs-sync reports nothing for this skill.
There is a companion PR adding ub-go. Both touch the shared catalog files (skill count and tables), so whichever lands second will need a small rebase; I can take care of that.
Same as with the Go PR: if any of this does not match how you want language skills to evolve (naming, scope, the lint starter approach, the reference split), I am happy to rework it. Feedback very welcome.