ReddRadar
Agent skill
check
Validates recently written code against project-specific development guidelines from .trellis/spec/. Identifies changed files via git diff, discovers applicable spec modules, runs lint and typecheck, and reports guideline violations. Use when code is written and needs quality verification, to catch context drift during long sessions, or before committing changes.
Install this agent skill to your Project
npx add-skill https://github.com/mindfold-ai/Trellis/tree/main/packages/cli/src/templates/qoder/skills/check
SKILL.md
Check if the code you just wrote follows the development guidelines.
Execute these steps:
-
Identify changed files:
bashgit diff --name-only HEAD -
Determine which spec modules apply based on the changed file paths:
bashpython3 ./.trellis/scripts/get_context.py --mode packages -
Read the spec index for each relevant module:
bashcat .trellis/spec/<package>/<layer>/index.mdFollow the "Quality Check" section in the index.
-
Read the specific guideline files referenced in the Quality Check section (e.g.,
quality-guidelines.md,conventions.md). The index is NOT the goal — it points you to the actual guideline files. Read those files and review your code against them. -
Run lint and typecheck for the affected package.
-
Report any violations and fix them if found.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
mindfold-ai/Trellis
create-command
Scaffolds a new skill file with proper naming conventions and structure. Analyzes requirements to determine skill type and generates appropriate content. Use when adding a new developer workflow skill, creating a custom skill, or extending the Trellis skill set.
mindfold-ai/Trellis
finish-work
Pre-commit quality checklist covering lint, typecheck, tests, code-spec sync, API changes, database migrations, cross-layer verification, and manual testing. Blocks commit if infra or cross-layer specs lack executable depth. Use when code is written and tested but not yet committed, before submitting changes, or as a final review before git commit.
mindfold-ai/Trellis
update-spec
Captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points. Use when a feature is implemented, a bug is fixed, a design decision is made, a new pattern is discovered, or cross-layer contracts change.
mindfold-ai/Trellis
check
Validates recently written code against project-specific development guidelines from .trellis/spec/. Identifies changed files via git diff, discovers applicable spec modules, runs lint and typecheck, and reports guideline violations. Use when code is written and needs quality verification, to catch context drift during long sessions, or before committing changes.
mindfold-ai/Trellis
check-cross-layer
Post-implementation verification across multiple code dimensions: cross-layer data flow, code reuse analysis, import path validation, and same-layer consistency checks. Identifies missed update sites, type mismatches, and duplicated constants. Use when changes span 3+ architectural layers, after modifying shared constants or configs, after batch file modifications, or when creating new utility functions.
mindfold-ai/Trellis
start
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.
Didn't find tool you were looking for?