LNSD
- 10 skills
- 0 followers
- 1 week ago last updated
- ▌ Feature Validate · lnsdVerify feature doc alignment with implementation. Use when asking about feature implementation status, or to check that documented functionality exists in code and has test coverage
- ▌ Feature Discovery · lnsdLoad relevant feature docs based on user query. Use when user asks about features, functionality, or how things work in the project.
- ▌ Docs Code Fmt Check · lnsdValidate guideline doc format against the specification. Use when reviewing PRs, after editing guideline docs, or before commits
- ▌ Docs Features Fmt Check · lnsdValidate feature doc format against the specification. Use when reviewing PRs, after editing feature docs, or before commits
- ▌ Commit · lnsdGenerate and validate conventional commit messages with Rust workspace scope rules. Use when user says "commit", "git commit", "/commit", asks for help with commit messages, or requests to amend a commit. Enforces crate-based scoping and validates message accuracy against changesets.
- ▌ Code Check · lnsdValidate and lint code after changes. Use after editing Rust files, when user mentions compilation errors, type checking, linting, clippy warnings, or before commits/PRs. Ensures all code passes checks and has zero warnings.
- ▌ Code Format · lnsdFormat Rust code automatically. Use immediately after editing .rs files, when user mentions formatting, code style, or before commits/PRs. Ensures consistent code style following project conventions.
- ▌ Code Review · lnsdReview code changes for bugs, guideline violations, security, and quality. Use when reviewing PRs, code changes, or before commits.
- ▌ Code Discovery · lnsdLoad relevant code guidelines based on user query or work context. Use when asking about code guidelines, standards, or before implementing code.
- ▌ Feature Status · lnsd bundleReport feature maturity and status. Use when asking about project status, feature readiness, or which features are stable/experimental/development