🚀 AI-powered Git auto commit & push CLI with smart commit messages
npm install @jashg91/gitpusherbash
npm install -g @jashg91/gitpusher
``
$3
`bash
gitpusher --version
// OR you can use
gipusher -v
`
---
🚀 Getting Started (Step-by-Step Setup)
$3
Go to GitPusher Dashboard and sign up with your email.
---
$3
* After login, add your API key in the dashboard.
* GitPusher securely stores your key in the DataBase (hashed) and gives you a one-time setup token.
* Copy this token — you’ll use it to link your CLI.
---
$3
In your project folder, run:
`bash
gitpusher config
? What would you like to do? (Use arrow keys)
❯ 🔑 Add Token
📊 View Usage Info
🔄 Sync Usage Cache
🗑️ Delete Configuration
❌ Exit
`
Choose “Add Token” and paste the token you copied from the dashboard.
GitPusher automatically:
* Validates your token with the backend
* Retrieves your encrypted API key
* Generates a local config file
🧱 Important:
Add this line to your .gitignore file:
`
gitpusher_config.json
gitpusher_usage_cache.json
`
This ensures your configuration never leaves your local system.
---
$3
`bash
Generate AI-powered commit message and push automatically
gitpusher "add new features"
Push to specific remote or branch
gitpusher "deploy to production" --remote origin
`
The CLI:
* Uses your securely stored API key for AI commits
* Tracks your usage
* Syncs data with the dashboard every 3 runs automatically
---
🔒 Security Highlights
| Layer | Protection | Description |
| --------------------------- | --------------------------------------- | -------------------------------------------- |
| API Key | 🔐 Hashed and never shown in plain text | Stored securely in backend |
| Dashboard Communication | 🍪 JWT in httpOnly cookie | Prevents frontend access to sensitive tokens |
| CLI Auth | 🧩 One-time setup token | Prevents direct key exposure |
| IP Verification | 🌍 IP stored during first use | Prevents token theft or key reuse |
| Config File | 🧱 Local only + gitignored | Prevents accidental upload to GitHub |
| Usage Sync | 🔁 Auto sync every 3 uses | Keeps analytics and usage limits accurate |
Every layer of GitPusher is designed to protect both your API credentials and your development environment.
---
🧠 How It Works (End-to-End Flow)
`text
[Frontend Dashboard] → [Backend Server] → [CLI Config] → [Git Operations] → [Dashboard Analytics]
`
$3
1. User registers/login on the GitPusher Dashboard.
2. Dashboard securely generates a hashed API key and returns a token to the user.
3. User runs gitpusher config in the CLI and enters that token.
4. CLI calls the backend to verify and store the API key securely in .gitpusher_config.json.
5. GitPusher performs smart git operations using that key (AI commits, pushes).
6. Every 3rd CLI use, usage data syncs back to the dashboard for analytics and tracking.
---
📊 Example Workflow
`
╭────────────────────────────────────────╮
│ 🚀 GitPusher │
╰────────────────────────────────────────╯
📋 Files to commit:
├────────────────────────────────────────
├── 📝 Modified: src/App.js
├── ➕ Added: src/utils/aiCommit.js
└── 📄 New: README.md
╰────────────────────────────────────────
✅ Files staged successfully
✅ Commit created: "feat: add AI-powered commit system"
✅ Pushed to origin/main
📊 Push Summary:
├── 🌿 Branch: main
├── 📡 Remote: origin
├── 💬 Message: feat: add AI-powered commit system
╰────────────────────────────────────────
🎉 Done! Synced with your dashboard.
``