.agents/skills/check/SKILL.md
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.
npx skillsauth add basui01/agentflow checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Check if the code you just wrote follows the development guidelines.
Execute these steps:
Identify changed files:
git diff --name-only HEAD
Determine which spec modules apply based on the changed file paths:
python3 ./.trellis/scripts/get_context.py --mode packages
Read the spec index for each relevant module:
cat .trellis/spec/<package>/<layer>/index.md
Follow 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.
development
Multi-agent pipeline orchestrator that plans and dispatches parallel development tasks to worktree agents. Reads project context, configures task directories with PRDs and jsonl context files, and launches isolated coding agents. Use when multiple independent features need parallel development, orchestrating worktree agents, or managing multi-agent coding pipelines.
development
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.
development
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.
development
Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.