Validate backend and frontend code locally before pushing commits.
npx skills add https://github.com/Bedriftsgrafen/bedriftsgrafen.no --skill safe-push
Please help me install this Agent Skill. Skill: Safe Push Source: https://github.com/Bedriftsgrafen/bedriftsgrafen.no/tree/main/.agent/skills/safe_push Command: npx skills add https://github.com/Bedriftsgrafen/bedriftsgrafen.no --skill safe-push
The Safe Push Skill reduces CI failures by ensuring code is validated locally before pushing, preventing hook fatigue and server overload.
Validate your changes locally before pushing to ensure CI stability.
High-intent search queries and answers about installing and using this skill.
To validate code locally before pushing, run formatting, linting, type checks, and targeted tests on backend and frontend changes prior to commit. This enforces mandatory local validation steps to prevent CI failures and server overload.
The best way to run pre-push checks is to apply specific validation commands for both backend and frontend components, ensuring formatting, linting, type checks, and targeted tests pass before committing code.
Pushing commits one by one helps reduce CI hook fatigue by using a safe, incremental push strategy that minimizes heavy jobs and retries, preventing server overload and ensuring CI stability.
Yes, you can run type checks and linting locally before a commit. The process guides developers through these validation steps to catch issues early and prevent CI failures.
No specific dependencies are required to run targeted tests locally before pushing. The validation process relies on your existing backend and frontend environment setup to execute the necessary checks.
MezzleConfigure BiomeJS linting, formatting, and code style via biome.json and npm scripts.
whilpTrigger and monitor GitHub Actions workflows via gh CLI.
Minara-AIConfigure Husky and lint-staged pre-commit hooks for JavaScript and TypeScript projects.
ANcpLuaRun local tests and monitor GitHub Actions CI before reporting completion.
