GitInProgress
io.github.ysk-abePublished by GitHub account ysk-abev0.1.3Updated Oct 25, 2026
Group your AI's changes into focused commit candidates; nothing lands until you approve.
Overview
GitInProgress is a VS Code extension that lets an AI draft reviewable commit candidates from a messy working tree, with nothing committed until you approve.
- What you can do
- Proposes how to split uncommitted changes into focused commit candidates for review before anything lands in history.
- When to use it
- When your working tree has mixed changes and you want an AI to suggest a clean commit split you can review and approve before committing.
- Requirements
- Runs as a local process on the user's machine and is desktop-only, tied to a VS Code extension. The extension's source is proprietary and not publicly available.
Installation
In SourceWeft
- Open GitInProgress in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
GitInProgress — Public Issue Tracker
This repository is the public issue tracker for GitInProgress, a VS Code extension where your AI drafts your commits as reviewable candidates: it proposes how to split a messy working tree into focused commits, and nothing lands in history until you approve.
The extension's source code is proprietary and not publicly available; this repository exists solely to receive bug reports, feature requests, and security disclosures from users.
Reporting a bug or requesting a feature
Open a new issue and choose the appropriate template:
- Bug report — for unexpected behavior or crashes
- Feature request — for new functionality
Please fill in all required fields. Issues without sufficient reproduction information may be closed after 7 days of inactivity.
Reporting a security vulnerability
Do not file public issues for security concerns. Use GitHub's private security reporting:
- Go to the Security tab of this repository
- Click "Report a vulnerability"
- Fill in the form
You should receive an acknowledgment within 7 days. See SECURITY.md for details.
Support level
GitInProgress is maintained by a single developer (solo dev). All triage and responses are best-effort — there is no SLA.
A dedicated email channel for Pro tier users will be added when the Pro tier launches in v1.0+.
License
The GitInProgress extension is distributed under the terms of its proprietary
LICENSE (included in the extension .vsix package). Note that this issue
tracker repository is intentionally source-code-free; the extension's
source is not publicly available.
Source: README.md at commit e4b63f2
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.