git-bootstrap
Skill1 starsChanged 6 months agoMITView on GitHub
Initialize git on a project, set up .gitignore, first commit, create the GitHub repo, push. Use when starting version control on any project for the first time.
- Reads credentials
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditSkill
- brainstormSkill
- commit-message-writerSkill
- compile-topicSkill
- course-builderSkill
- daily-note-writerSkill
- deck-builderSkill
- diagnoseSkill
- drift-fixSkill
- forgeSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- lesson-content-writerSkill
- project-scaffolderSkill
- prototypeSkill
- retroSkill
- reviveSkill
- setup-pre-commitSkill
- specialist-creatorSkill
- sweep-inboxSkill
- tddSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- workflow-authorSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 12
Run the existing script:
- Very specific: line 17
Add -Public if shareable.
- Distinctive: line 24
Don't init without .gitignore (sweeps junk)
- Distinctive: line 25
Don't commit secrets - check .env / API keys first
- Distinctive: line 26
Don't push vault publicly (personal memory + activity log)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git Bootstrap
When to use
Triggers: git init, set up git, bootstrap git, put this on GitHub.
Preferred path
Run the existing script:
cd "<project-path>"
& "E:\Projects\AI Knowledge Base\22 - Scripts\git-bootstrap.ps1" -Path "<project-path>" -Name "<repo-name>"Add -Public if shareable.
Per-project visibility defaults
- AI Knowledge Base, TerraWatt, KSP*, Command Center:
private - Fundamentals of Coding:
publicwhen ready
Don't
- Don't init without .gitignore (sweeps junk)
- Don't commit secrets - check .env / API keys first
- Don't push vault publicly (personal memory + activity log)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

