ASD v1.1.3
ASD is a natural language Git assistant for the terminal. It translates plain English instructions into Git commands, helping you manage branches, histories, and merges safely and efficiently.
Why ASD?
- I struggled with Git’s commands and conflicts.
- I wanted a simple, transparent tool—no magic—just clear steps.
Features
- Translate English instructions into Git commands.
- Guide complex workflows with best-practice suggestions.
- Visualize commit graphs and branch histories.
- Offer safety checks and recovery guidance for risky operations.
Getting Started
Installation
From PyPI:
pip install git-asd
Or directly from GitHub:
pip install git+https://github.com/adikuma/asd.git
Launch
asd
This opens ASD’s interactive terminal interface. Enter any Git task in plain English.
Workflow
Here’s a quick look at the five-step process inside ASD:
flowchart LR
Start([Start]) --> Analyze[Analyze Git Context]
Analyze --> Intent[Parse User Intent]
Intent --> Plan[Generate Execution Plan]
Plan --> Review[Review Plan & Status]
Review --> Execute[Execute Commands]
Execute --> End([End])
- Analyze Git Context: Examine
git statusto capture your repository’s state. - Parse User Intent: Turn your English request into a structured plan.
- Generate Execution Plan:Create a safe list of Git commands.
- Review Plan & Status: Inspect the plan and current status.
- Execute Commands: Run each step with your approval and mini-lessons.
Roadmap
ASD is an early project with plenty of room for improvement. I would love to have people test it, report issues, and suggest features so I can refine and expand its capabilities.
Contributions and feedback are welcome. Please open an issue or submit a pull request.
Contribution Guidelines
This is my general contribution process; I like to keep it simple—sorry about that :)
| Topic | Guidelines |
|---|---|
| Branching Strategy | feature/ for new features (e.g., feature/add-login-command), fix/ for bug fixes (e.g., fix/handle-empty-input). |
| Code Formatting | Use [ruff] for formatting. Run ruff format . before pushing. |
| Code Style | Keep comments lowercase; use # NOTE: or # TODO: for import-related comments. |
| Commit Messages | FollowConventional Commits specification. |
| Pull Requests & Merging | Create a PR; merging to main requires ≥1 collaborator approval; use squash merge. |
| Creativity | Feel free to experiment and innovate. |
Updates
For a detailed change history, see UPDATES.md.
Metadata
Release files for git-asd 1.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| git_asd-1.1.3.tar.gz | 26.0 kB | Without provenance | Details for git_asd-1.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_asd-1.1.3-py3-none-any.whl | Python 3 | none | any | Details for git_asd-1.1.3-py3-none-any.whl |
Total release size: 54.8 kB
Release files / git_asd-1.1.3.tar.gz
| Download URL | git_asd-1.1.3.tar.gz |
|---|---|
| Size | 26.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9d347b7c8f33124bb0e715e7d1003859215e8108c37904e88e311a7c140d3da
|
|
BLAKE2b-256 checksum How to use checksums |
0b48acf8829ff1554aed600248062cad8c379a50f5cc4094205b957bf0e49745
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.5
|
Release files / git_asd-1.1.3-py3-none-any.whl
| Download URL | git_asd-1.1.3-py3-none-any.whl |
|---|---|
| Size | 28.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2dd4e37e9e78e78c35bfbafb98786b97265141b2091ac8231857c29a7ef4a65
|
|
BLAKE2b-256 checksum How to use checksums |
a1f3b7f414fb7ad29de354f44e733d4f4f2aa6ebd00b504fed95ca4889c1c389
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.5
|
Security for git-asd 1.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.