Problem
What problem this solves
A change can look complete in the editor while still failing basic project checks that matter for real delivery.
Skill Detail
Run the standard technical checks and fix the obvious issues before you pretend the work is done.
A practical quality gate for typecheck, lint, build, and related technical validation in the current project.
Problem
A change can look complete in the editor while still failing basic project checks that matter for real delivery.
Outcome
You get a tighter technical validation loop and earlier visibility into build-breaking or type-breaking issues.
Why It Matters
This skill is useful when you need a concrete technical stoplight before moving to higher-level review or shipping.
Related Skills
Use one explicit technical mode for code risk, dependencies, performance, or a breaking migration.
A unified technical entrypoint with four bounded modes and evidence limits that match the work.
Open skill pageOpen a URL in a real browser and verify one observable non-auth objective.
A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.
Open skill pageCheck whether the work really satisfies the user story, not just whether the code compiles.
A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.
Open skill pageStart implementation when the task is ready, and force a stronger path when it is not.
The main execution entrypoint for beginning real work after the problem and contract are clear enough, while keeping the chantier flow visible.
Open skill pageCommit and push quickly when the work is actually ready, instead of stretching closure into another vague step.
A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.
Open skill pageGo Deeper
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.