git-push

Run lint, format, tests, and type checks before pushing to Git.

7|1|Updated Mar 30, 2024
One-click install
npx skills add https://github.com/Lionad-Morotar/simple-local-llm-server --skill git-push-lionad-morotar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-push
Source: https://github.com/Lionad-Morotar/simple-local-llm-server/tree/main/local-link/skills/git-push
Command: npx skills add https://github.com/Lionad-Morotar/simple-local-llm-server --skill git-push-lionad-morotar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git pre-push checks on codebases are error-prone and slow down collaboration; this skill automates detection, fixes, and enforcement before pushing.

Core Features & Use Cases

  • Automatic checks before push: Run lint, format, tests, check-types on changed files.
  • Auto-fix when possible: Apply fixes and re-run checks until success or manual intervention.
  • Safe push control: Push only when checks pass; otherwise report issues or create PR.

Quick Start

Trigger the pre-push workflow to detect changes, run checks, auto-fix when possible, and push when all checks pass.

Frequently Asked Questions about git-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate lint and format checks before a git push?

Automating pre-push checks involves detecting changed files and running lint, format, test, and type checks before pushing to a remote repository. This process applies fixes and re-runs checks until success or manual intervention is needed.

Can I auto-fix linting and formatting errors before pushing to remote?

Yes, you can auto-fix linting and formatting errors before pushing to remote. The workflow attempts automated corrections on changed files, rechecks the code, and pushes only when all checks pass.

What happens to my git push if type checks or tests fail?

If type checks or tests fail, the git push is blocked to ensure code quality. The workflow reports the issues for manual resolution or creates a PR instead of pushing to the remote repository.

Does this pre-push workflow run on changed files only or the entire codebase?

The pre-push workflow runs checks on changed files only. By detecting changes first, it applies lint, format, test, and type checks specifically to your modifications before attempting to push.

How do I enforce code quality checks across team projects before push?

To enforce code quality across team projects, configure a pre-push workflow that runs lint, format, tests, and type checks on changed files. It safely controls the push, ensuring no unverified code reaches the remote repository.