0% found this document useful (0 votes)
7 views4 pages

C Users Vivek Source Repos APIAPI

The document provides troubleshooting steps for resolving the 'spawn git ENOENT' error encountered when using the skills CLI on Windows. It suggests installing Git for Windows and ensuring it is added to the system PATH. If Git is already installed but not recognized, it advises adding the appropriate Git directories to the PATH and verifying the installation before retrying the command.

Uploaded by

Kingsman Potter
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views4 pages

C Users Vivek Source Repos APIAPI

The document provides troubleshooting steps for resolving the 'spawn git ENOENT' error encountered when using the skills CLI on Windows. It suggests installing Git for Windows and ensuring it is added to the system PATH. If Git is already installed but not recognized, it advises adding the appropriate Git directories to the PATH and verifying the installation before retrying the command.

Uploaded by

Kingsman Potter
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

C:\Users\vivek\source\repos\API\API>npx

skills@latest add github/awesome-copilot --skill


aspnet-minimal-api-openapi -y
███████╗██╗ ██╗██╗██╗ ██╗ ███████╗
██╔════╝██║ ██╔╝██║██║ ██║ ██╔════╝
███████╗█████╔╝ ██║██║ ██║ ███████╗
╚════██║██╔═██╗ ██║██║ ██║ ╚════██║
███████║██║ ██╗██║███████╗███████╗███████║
╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝╚══════╝

T skills
|
o Source: [Link]
|
|
x Failed to clone repository
|

Failed to clone [Link] Error: spawn git ENOENT

at ChildProcess._handle.onexit (node:internal/child_process:286:19)

at onErrorNT (node:internal/child_process:507:16)

at [Link] (node:internal/process/task_queues:90:21)

Tip: use the --yes (-y) and --global (-g) flags to install without prompts.

— Installation failed

x Canceled

C:\Users\vivek\source\repos\API\API>

The error is clear: spawn git ENOENT means the skills CLI tried to run Git, but Windows could
not find [Link] in your PATH. So npx skills is working, but Git is either not installed or not
added to PATH. [1] [2]
Fix it
Install Git for Windows, then reopen the terminal and verify with git --version. The official
Git for Windows install page gives this Winget command: winget install --id [Link] -e --
source winget. [3]

Run these in PowerShell or CMD:

winget install --id [Link] -e --source winget

Then close the terminal, open a new one, and run:

git --version
where git

If git --version works, retry:

npx skills@latest add github/awesom e-copilot --skill aspnet-m inim al-api-openapi -y

If Git is already installed


Sometimes Git is installed but not on PATH, which is a common cause of spawn git ENOENT on
Windows. In that case, add these folders to your PATH, then restart the terminal: [4] [5] [1]

C:\Program Files\Git\cm d
C:\Program Files\Git\bin

After that, test again:

git --version

Important note
If you only have GitHub Desktop, that may still not be enough because GitHub Desktop does
not reliably expose a command-line [Link] for other tools, and its own issue tracker
recommends installing Git for Windows and ensuring the installer adds Git to PATH. So the
safest fix is to install Git for Windows directly. [6] [3]

Exact steps
1. Open PowerShell as normal.
2. Run winget install --id [Link] -e --source winget. [3]
3. Close all terminals.
4. Open a fresh terminal in C:\Users\vivek\source\repos\API\API.
5. Run git --version.
6. Run your npx skills@latest add ... command again. [1] [3]
If git --version still fails after install, paste the output of these two commands:

git --version
$env:Path

1. [Link]
2. [Link]
awn-git-enoent
3. [Link]
4. [Link]
5. [Link]
6. [Link]
7. [Link]
8. [Link]
9. [Link]
10. [Link]
11. [Link]
12. [Link]
13. [Link]
14. [Link]
15. [Link]
ed-error
16. [Link]
17. [Link]
18. [Link]
19. [Link]
20. [Link]
21. [Link]
22. [Link]
23. [Link]
24. [Link]
25. [Link]
26. [Link]

You might also like