t-push

Summarize git diff changes into commit messages and run local CI before pushing.

64|6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/timzaak/web-dev-skills --skill t-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t-push
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-push
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-push

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

由 AI 基于 git diff 总结提交内容,自动执行本地 CI,确保通过后再 git commit 并 git push。

Core Features & Use Cases

  • 基于 git diff 自动生成简洁 commit message
  • 针对受影响区域运行本地 CI
  • CI 全部通过后执行 git commit 与 push

Quick Start

让 AI 总结本次改动并在本地 CI 通过后执行推送。

Frequently Asked Questions about t-push

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

FAQPage Schema
How do I automate git commit message generation from diff?

You can automate git commit message generation by having AI summarize git diff changes into a concise message. It reads repository status and creates a commit message reflecting the actual code modifications.

Can I run local CI scripts before git push automatically?

Yes, you can run local CI scripts before git push automatically. The system executes local CI for affected areas, validating backend and frontend tests, and only commits and pushes after successful validation.

How does AI summarize git diff for feature branches and hotfixes?

AI summarizes git diff for feature branches and hotfixes by analyzing the changes and generating a concise commit message. It validates changes across backend and frontend tests before committing and pushing.

Do I need local CI scripts to use automated git push?

Yes, you need access to the repository and local CI scripts to use automated git push. The system requires these to read status, perform tests for affected areas, and push only after successful validation.

What happens if local CI tests fail during automated commit?

If local CI tests fail during automated commit, the process stops and does not execute git commit or git push. The system ensures all backend and frontend tests pass before applying changes to the repository.

Is automated git push suitable for both frontend and backend changes?

Yes, automated git push is suitable for both frontend and backend changes. It validates changes across both frontend and backend tests before committing, ensuring comprehensive coverage for feature branches and hotfix flows.