agentsclimarketplace
Sign in

Pre push check

Skill AndreJorgeLopes/devflow/skills/pre-push-check

Run the full pre-push review pipeline — code review checks, self-review against CLAUDE.md, and a final report.From its SKILL.md

Install
npx -y skills add AndreJorgeLopes/devflow --skill pre-push-check

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, as published. Nobody here has run it

You are about to push code. Run the full pre-push quality pipeline before pushing.

Steps

  1. Check what's being pushed. Run git diff --stat and git log --oneline origin/HEAD..HEAD to understand the scope of changes.

  2. Run code review checks. Execute:

    devflow check

    Capture and parse the output. This uses Claude Code (primary) or OpenCode (fallback) to review against .devflow/checks/*.md rules. If neither CLI is available, fall back to running the project's lint and type-check commands directly (e.g., yarn lint, yarn build).

  3. Self-review the diff against CLAUDE.md. Read the project's CLAUDE.md file and review the staged changes against its rules:

    • Scope discipline: every changed line traces to the task. No speculative abstractions, no adjacent refactors, no dead-code removals beyond orphans created by this change.
    • Are naming conventions followed?
    • Are the architectural patterns respected (clean architecture layers)?
    • Are imports using the correct path aliases?
    • Is error handling done properly (no raw console.log, proper error classes)?
    • Are there any hardcoded secrets or credentials?
    • Is input validation present where needed?
    • Are tests included for new functionality?

  4. Check for common issues:

    • Files that shouldn't be committed (.env, credentials, node_modules)
    • console.log statements left in production code
    • any type usage in TypeScript
    • Missing error handling in async functions
    • TODOs without ticket references

  5. Generate the report:

    ## Pre-Push Check Report

**Branch:** [branch name]
**Commits:** [number] commits ahead of origin

 ### Code Review Results
- [PASS/FAIL] [details]

### CLAUDE.md Compliance
- [PASS/WARN/FAIL] Scope discipline (every line traces to task)
- [PASS/WARN/FAIL] Naming conventions
- [PASS/WARN/FAIL] Architecture patterns
- [PASS/WARN/FAIL] Import paths
- [PASS/WARN/FAIL] Error handling
- [PASS/WARN/FAIL] Security
- [PASS/WARN/FAIL] Test coverage

### Issues Found
- [list of issues, if any]

### Verdict: [READY TO PUSH / NEEDS FIXES]

  6. If issues are found, list them clearly and ask the user if they want to fix them before pushing. If everything is clean, confirm it's safe to push.

$ARGUMENTS

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.