code-quality
Run pre-push validation before pushing code. MANDATORY before every git push.
- License 许可
- MIT
- 最近更新
- 2026-03-11
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- code-quality
- description
- Run pre-push validation before pushing code. MANDATORY before every git push.
- allowed-tools
- Bash
02 资源文件 2
- 参考文档ACKNOWLEDGEMENTS.md3.0 KB
- 其他SKILL.md.tmpl34.2 KB
03 SKILL.md 正文
Code Quality Checks
Pre-Push Validation (MANDATORY)
Before every git push, run your project's quality checks.
Look for these in the repo (try in order):
- A
pre-push-validateorlintnpm script:npm run lint - A Makefile target:
make lint - Common linters:
[ -f .eslintrc* ] && npx eslint . --fix [ -f .prettierrc* ] && npx prettier --write .
Only push if ALL checks pass. This prevents CI failures.
Incremental Commits
Commit after every file change to avoid losing work:
git add <file> && git commit -m "WIP: description" && git push
This is especially important under budget constraints — uncommitted work is LOST if the session terminates.
04 同仓库更多 Skills
story-workflow
9-phase workflow for implementing user stories. Covers requirements through verification.
rfs-proposal
File a Request for Skill (RFS) when a skill gap is detected during execution.
review-handling
Process review comments from AI review or human reviewers. Evaluate, respond, and resolve or escalate.
pr-creation
Create GitHub pull requests with proper format.
playwright-verify
Browser verification using Playwright MCP. Navigate, interact, screenshot.
merge-conflicts
Resolve merge conflicts by rebasing. Use when PR mergeable status is CONFLICTING.