Verifies code quality through spec compliance, lint, tests, and cross-layer checks.
npx skills add https://github.com/MaplumeX/Milesto --skill trellis-check-maplumex
Please help me install this Agent Skill. Skill: trellis-check Source: https://github.com/MaplumeX/Milesto/tree/main/.agents/skills/trellis-check Command: npx skills add https://github.com/MaplumeX/Milesto --skill trellis-check-maplumex
.trellis/spec/ for each changed package or layer and checks the code against documented quality guidelines. - Project Checks: Runs the project's lint, type-check, and test commands and requires all failures to be fixed before proceeding. - Cross-Layer Analysis: Traces data flow across Storage, Service, API, and UI layers, checks code reuse, import correctness, and same-layer consistency. - Use Case: Before committing a feature that touches the database worker, IPC layer, and React UI, run this Skill to confirm types propagate correctly, tests cover the new behavior, and specs are updated with any lessons learned. ## Quick Start Run the trellis-check skill to verify the quality of my recent uncommitted changes before I commit them.High-intent search queries and answers about installing and using this skill.
Run a structured check that identifies changed files via git diff, reads applicable specs, executes the project's lint, type-check, and test commands, and reviews a checklist covering debug logging, test coverage, and spec synchronization before committing.
Trace read flows from Storage through Service and API to UI, and write flows in reverse. Verify that types and schemas pass correctly between layers and that errors propagate properly to the caller at each boundary.
A pre-commit checklist should confirm linter and type checker pass, tests pass, no debug logging remains, new functions have unit tests, bug fixes have regression tests, and documentation or specs are updated with non-obvious lessons learned.
Skip cross-layer checks when your change is confined to a single layer, such as a UI-only styling fix. These checks only apply when changes touch three or more layers, modify shared constants, or create new files with import dependencies.
Search the codebase with grep for existing similar patterns before writing new utilities. If two or more places define the same value, extract it into a shared constant, and after batch modifications verify all occurrences were updated.
HexalithReviews code changes with parallel independent reviewers, then triages and presents findings.
greencmMerge pull requests, run CI tests, and deploy to production with canary checks.
michael-watsonUpdate AGENTS.md and HOWTOAI.md after significant implementation changes.
MathiasPaulenkoEnforce SonarQube quality gates and static analysis in CI/CD pipelines.