After spending hours on implementing a feature, the code works, tests pass, I'm feeling good. Time to commit and push:
git add .
git commit -m "feat: add oauth"
git push
Done, right?
Nope.
Now I gotta open Jira. Find the ticket. Click into it. Write a detailed technical implementation summary, and change status from "In Progress" to "In Review". Then, tag the QA team. Log my hours. Click submit.
Finally done.
This happens 5-6 times a day. Every single day.
After doing this for the millionth time, I thought: Why am I doing all this paperwork? And why am I context-switching to a browser just to fill out forms?
What I Tried First
I looked for existing solutions. Found Cursor's Jira MCP more feasible. Tried it.
It does some things well - you can ask Cursor to fetch ticket details, update status, and add comments without opening a browser. But it didn't solve my actual problem:
The limitations I hit:
- Git workflow – I prefer the terminal over Cursor for Git operations.
- Manual interaction required - Each Jira update needs a chat command. which is again time-consuming and boring for me
- Context switching to Cursor - Had to be inside the IDE. If I'm in the terminal doing git work, I'd have to switch to Cursor just for Jira updates.
- Custom field setup is painful - Time tracking fields, story points, and custom estimates all need explicit configuration.
- Chat-based workflow - Doesn't fit the "just commit and be done" flow I wanted
I wanted something simpler. Something that lives in my terminal where I already am. Something that automatically updates Jira when I push code, without me having to think about it.
So I built a CLI for it - GitQuick
What It Does
gq cp
One command. It:
- Generates a proper commit message by analyzing my actual code changes and ticket details
- Pushes to remote
- Updates the Jira ticket automatically
- Logs time, changes status, technical summary, whatever you need
15 seconds instead of 5 minutes. No browser required.
Why I Built This
I don’t hate Jira. I hate that after pushing code, I still have to open a browser and write a detailed technical summary.
Here’s the actual workflow: I’d commit, push, then go to Jira and write implementation details, what changed, the technical approach, and testing notes. This part took the longest — about 3–5 minutes of writing out the same technical context I already had in my head while coding.
And I’d forget to do it. Or I’d do it hours later, after I’d already moved on to something else and had to reconstruct what I did.
GitQuick fixes this.
How It Actually Works
Starting a New Ticket
# See what's in your backlog
gq jira list
# Create a branch from the ticket
gq branch DH-1234
It fetches the Jira ticket, figures out if it's a feature or bugfix, and creates something like:
feature/ID-1234-implement-oauth-authentication
The ticket ID is now in the branch name. Every command after this knows which Jira ticket to update. I don't have to keep specifying it.
Making Changes and Committing
# After you make your changes:
gq
The AI looks at your git diff and generates a commit message. Yeah, AI commit messages are sometimes cool. Not always
feat(auth): ID-1234 implement OAuth 2.0 authentication with JWT tokens
- Add OAuth2 provider configuration
- Implement token refresh mechanism
- Add secure session management
Pushing and Updating Jira
gq push
Or better yet:
gq cp # commit + push in one go
It pushes your code and asks: "Update Jira ticket ID-1234?"
You say yes. It posts a comment with what you changed, updates the status, logs your time - whatever you configured.
No browser. No context switch. Just keep coding.
The Time Math
I commit about 5-6 times a day. That's 30 minutes saved daily. 100 minutes weekly.
Over a year? About 85 hours. That's more than two full work weeks I'm not spending on admin work.
Setup Takes 2 Minutes
git clone https://github.com/vishnu-sp/GitQuick.git
cd GitQuick
./git-cli.sh init
- Pick your shell (zsh or bash)
- Choose your AI provider
- Add your API key (stored in macOS Keychain or .env)
- Configure Jira (email, API token, base URL)
That's it. Start using gq immediately.
Things I Like About My Own Tool
It doesn't force a workflow. I can use just the commit part. Or just the Jira part. Or everything. Your choice.
Multiple Jira instances. I work with client Jira instances. I can configure multiple and switch between them:
gq jira add client https://client.atlassian.net
gq jira select
Try It
Repo: github.com/vishnu-sp/GitQuick
If you're tired of updating Jira manually, give it a shot. If you find bugs or want features, open an issue. If you want to contribute, PRs are welcome.