Validate changed files against project-specific development guidelines with lint and typecheck.
npx skills add https://github.com/Jerry-Z07/WindBoard --skill check-jerry-z07
Please help me install this Agent Skill. Skill: check Source: https://github.com/Jerry-Z07/WindBoard/tree/main/.agents/skills/check Command: npx skills add https://github.com/Jerry-Z07/WindBoard --skill check-jerry-z07
Validates recent code changes against project-specific development guidelines to prevent context drift and ensure code quality before commits.
Use Case: Before committing or pushing a change, run this check to ensure adherence to guidelines and reduce review cycles.
Run a quick quality check on your latest changes to ensure they conform to the project's development guidelines before committing.
High-intent search queries and answers about installing and using this skill.
To validate code changes against project guidelines, run a check that diffs modified files, selects applicable spec modules, and executes lint and typecheck to report violations before committing.
Automating lint and typecheck for pre-commit code review involves diffing changes via git diff HEAD, locating relevant modules under spec directories, and running language-specific checks to catch style and type errors before merging.
Git diff scoping for CI pipeline quality assurance works by identifying modified files with git diff HEAD to limit reviews to changed files, then applying path-based logic to discover applicable spec modules for targeted linting.
Yes, you can catch style guideline violations across changed files only by applying the check during local development or pre-commit to surface actionable feedback on affected modules without reviewing the entire codebase.
No specific dependencies are required to run typecheck on affected spec modules, as the check applies path-based logic to locate relevant modules and executes language-specific checks natively within your environment.
You should run quality assurance checks on changed files before pushing to CI to prevent context drift, ensure adherence to development guidelines, and reduce review cycles by catching lint and style issues early.
SilentFlowerRun lint and typecheck on git-changed packages against .trellis/spec guidelines.
darknightCommit staged Git changes after passing lint checks.
maltemdManage documentation with version control, CI/CD, and automated testing workflows.
LayerDynamicsReview current git diff changes for bugs, security issues, and style inconsistencies.
