Verify lint, type-check, tests, and data-flow quality gates for changed code.
npx skills add https://github.com/Tendo33/IdeaGo --skill trellis-check-tendo33
Please help me install this Agent Skill. Skill: trellis-check Source: https://github.com/Tendo33/IdeaGo/tree/main/.agents/skills/trellis-check Command: npx skills add https://github.com/Tendo33/IdeaGo --skill trellis-check-tendo33
Automates comprehensive quality verification to ensure newly written code meets specifications, passes lint and type checks, runs tests, and preserves cross-layer data flow and code reuse integrity.
Run the trellis-check workflow on changed packages to validate lint, type-checks, and tests before committing.
High-intent search queries and answers about installing and using this skill.
You can automate code quality verification by running a workflow that compares code diffs against specs and applies lint, type-check, and test execution to changed packages. This process ensures consistency, prevents regressions, and guards against unsafe changes before committing.
Cross-layer data-flow validation checks consistency across your codebase to catch context drift during code review. You need it when newly written code risks breaking data flow between layers, ensuring specifications are met and regressions are prevented.
Yes, you can use automated lint and type-check enforcement in CI pipelines to prevent regressions. The workflow validates changed code against specifications, runs project checks, documents failures, and guides fixes to ensure newly written code meets quality gates.
The best way to verify spec compliance is to compare code diffs against specifications while running lint, type-check, and tests. This end-to-end quality verification enforces checklist completion, documents failures, and guides fixes to ensure consistency across the codebase.
Your code review workflow misses context drift because it lacks cross-layer data-flow validation. By comparing diffs against specs and validating consistency across the codebase, you can catch context drift, document failures, and guide fixes to prevent regressions.
No, you do not need external dependencies to run end-to-end quality verification. The workflow independently compares diffs against specs, applies lint and type-checks, runs tests, and validates cross-layer data flow to ensure code quality without requiring additional setup.
iiammaeCompare blockchain smart contract source code against specification documents for compliance.
signalcomposeOrchestrate a multi-agent team for pull-request reviews with CI/CD integration and iterative fix loops.
s-hiraokuAutomate Ruff linting, Mypy type-checking, and Pytest tests on changed Python files.
jfrometaRun lint, type checks, and security audits on Node.js and Python projects.
