\\\\\\
\\\\\\\\\\\\
\\\\\\\\\\\\\\\
-------------,-| |C> // )\\\\| .o88b. db db .d8b. db db .d8b. d888888b d888888b d88888b
,','| / || ,'/////| d8P Y8 88 88 d8' '8b 88 88 d8' '8b '~~88~~' '~~88~~' 88'
---------,',' | (, || ///// 8P 88ooo88 88ooo88 Y8 8P 88ooo88 88 88 88ooooo
|| | \\ ||||//''''| 8b 88~~~88 88~~~88 '8b d8' 88~~~88 88 88 88~~~~~
|| | ||||||| _| Y8b d8 88 88 88 88 '8bd8' 88 88 88 88 88.
|| |______ ''''\____/ \ 'Y88P' YP YP YP YP YP YP YP YP YP Y88888P
|| | ,| _/_____/ \
|| ,' ,' | / | ___________________________________________
||,' ,' | | \ | / \ \
_________|/ ,' | / | | | | |
_____________,' ,',_____| | | | \ | chavatte@duck.com |
| ,',' | | | | | chavatte.vercel.app |
| ,',' ____|_____/ / | | ________________________________________|___
| ,',' __/ | / | | / /
_____________|',' ///_/-------------/ | \_/____________________________________________/
|===========,'
- Overview
- Architecture & Features
- Prerequisites
- Installation & Global Setup
- Command Reference
- DevSecOps Use Cases
- Security Policy
Sentinel Git-OPS, developed by Chavatte Security, is an interactive, menu-driven Command Line Interface designed to harden and automate the Git development lifecycle.
By replacing raw, repetitive Git commands with a guided terminal experience, Sentinel minimizes operational human errors (e.g., accidental pushes to main, unreviewed commits) and introduces DevSecOps principles directly into the developer's daily workflow.
Built with Clean Code principles, v2.3.0 introduces a highly modular architecture where the core router is strictly separated from logical actions and dynamic i18n dictionaries.
- 📊 Tactical Dashboard: Real-time telemetry displaying the current node (branch), file modification status, and connected cloud networks directly in the terminal header.
- 🛡️ Shield Ops (Pre-Commit Hook): Injects a security script to actively scan and block commits containing exposed secrets (AWS keys, RSA keys, GitHub tokens).
- 🔄 Self-Update Protocol: Keep your CLI updated with a single keystroke using the built-in self-pull mechanism.
- 🌐 Omnicast Multi-Push: Added extended support for GitLab and Keybase as additional network infrastructures. Deploy your codebase simultaneously across multiple remote environments by simply targeting
ALL. - 🔐 Auth-Ops & Authorization Layer: Independent identity management module with native support for CLI login and authorization across GitHub, GitLab, and Keybase. Forge highly secure
Ed25519SSH keys directly from the tool. - 💻 True Cross-Platform: Native execution environments for Windows (PowerShell) and Linux/macOS (Bash/Zsh).
- 🌍 Native i18n: Swap between English and Portuguese interfaces in real-time.
Ensure your environment meets the following requirements before deploying Sentinel:
- Git
v2.0or higher. - Windows: PowerShell
5.1or PowerShell Core7+. - Linux/macOS: Standard
bashorzshenvironment. - (Optional) GitHub CLI (
gh), GitLab CLI (glab), or Keybase app for the Auth-Ops module.
Sentinel Git-OPS features a built-in global injector. You do not need to manually configure your PATH.
# 1. Clone the repository
git clone https://github.com/chavatte/sentinel-git-ops.git
cd sentinel-git-ops
# 2. Launch the terminal
.\win\git-ops.ps1Make it Global: Once the menu is open, select option
[12] INSTALL. Sentinel will automatically configure your Execution Policies and inject its alias into your$PROFILE.
# 1. Clone the repository
git clone https://github.com/chavatte/sentinel-git-ops.git
cd sentinel-git-ops
# 2. Grant execution permissions
chmod +x linux/git-ops.sh linux/core/*.sh
# 3. Launch the terminal
./linux/git-ops.sh
Make it Global: Select option
[12] INSTALL. Sentinel will write an alias directly into your~/.bashrcor~/.zshrc.
| Category | Command | Description |
|---|---|---|
| Workflow | 1. INITIATE |
Provisions a new branch and links it to the remote instantly. |
| Workflow | 2. COMMIT |
Scans modifications, stages, and commits changes securely. |
| Workflow | 3. DEPLOY |
Switches to main, pulls updates, merges the feature, and pushes. |
| Workflow | 4. PURGE |
Safely deletes a local branch to maintain node hygiene. |
| Workflow | 5. SWITCH |
Interactive checkout between existing local nodes. |
| Tactical | 6. STATUS |
Displays repository health and the recent chronological commit tree. |
| Tactical | 7. STASH |
Quick access to stash push, pop, and list commands. |
| Tactical | 8. AUDIT |
Triggers git diffto inspect code line-by-line before committing. |
| Tactical | 9. RADAR |
Runs a passive git fetch --allto check for remote cloud updates. |
| Tactical | 10. REVERT |
**Panic Button:**Soft resets HEAD~1, keeping files in the staging area. |
| Tactical | 11. DISCARD |
**Destruction Protocol:**Drops all uncommitted local changes. |
| System | 12. INSTALL |
Injects the terminal alias globally into your system. |
| System | 13. LANG |
Toggles UI language (EN / PT-BR). |
| System | 14. NETWORK |
Manage remotes and enable Omnicast Multi-Push routing. |
| System | 15. AUTH |
Manage Credentials and forge secure SSH keys (Ed25519). |
| System | 16. UPDATE |
**Self-Update:**Automatically pulls the latest Sentinel version. |
| System | 17. SHIELD |
**Shield Ops:**Injects a pre-commit hook to block secret leaks. |
Relying on a single point of failure for your source code is a security risk.
- Open the terminal and select
14( NETWORK ). - Choose
1to link a new remote (e.g., name itgitlaband paste the URL). - During any
INITIATEorDEPLOYoperation, when prompted for the target remote, typeALL. - Sentinel will broadcast your code to both GitHub and GitLab simultaneously.
Ensure secrets never make it to your remote repository.
- Run option
17( SHIELD ) inside your project. - If a developer attempts to commit an exposed credential (like an AWS key or GitHub token), Sentinel intercepts the process.
- The commit is instantly blocked with an alert detailing the file and the matched secret pattern.
If you accidentally staged a broken function or need to rework your last commit:
- Immediately press
10( REVERT ). - Sentinel executes a surgical
git reset --soft HEAD~1. - The commit is erased from history, but your files remain staged. Make the necessary fixes, and use
2( COMMIT ) to create a clean, safe record.
As a project maintained by Chavatte Security , we take the integrity of our tools seriously. If you discover a vulnerability or a potential attack vector within the CLI scripts (e.g., command injection flaws), please do not open a public issue.
Instead, contact the maintainer directly to arrange a secure disclosure.
This project is distributed under the MIT license. See the LICENSE file for details.
