Smithery is now a part of Arcade.dev! Read more in our announcement here
Verify main branch stability before development and before pushing code to remote.
This skill verifies that the codebase is in a stable state. It should be run:
Run at the start of any implementation workflow, after checking out and pulling main:
1. Read PROJECT.md
2. Look for a section called 'Stability Checks'
3. If found, follow those directions for the "preparation" phase
4. If not found, look for make/task/just targets with the word "sanity" and run the first one you find
5. If there are multiple build tools, run the first sanity target you find for each build tool
Run after implementation and testing, but before pushing to remote:
1. Read PROJECT.md
2. Look for a section called 'Stability Checks'
3. If found, follow those directions for the "pre-push" phase
4. If not found, run the same sanity targets as in preparation phase
5. This catches any regressions introduced by your changes
A PROJECT.md file might define stability checks like this:
## Stability Checks
### Preparation Phase
Run these before starting development:
- `make lint` - Verify linting passes
- `make test` - Run unit tests
### Pre-Push Phase
Run these before pushing code:
- `make lint` - Verify no new linting issues
- `make test` - Verify no test regressions
- `make build` - Verify build succeeds
If no PROJECT.md exists or no 'Stability Checks' section is found:
make sanity, task sanity, just sanityAgents should invoke this skill at two points:
git pull origin main, before creating feature branchgit push