github-repo-publish
Skill2 starsChanged 8 days agoMITView on GitHub
Standard procedure for initialising and publishing a new GitHub repository in the pranataa-labs ecosystem: English kebab-case naming, safe .gitignore, first commit with the mandatory co-author trailer, gh repo create, collaborator invitation for ariasastra-dev (Rule 12.1), topic sync (Rule 11.1), and optional Branch and PR flow. Use whenever the user asks to create a repo, publish/push a project to GitHub, rename a repository, or set up collaborators.
- Reads credentials
- Commits and pushes
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jgobuilds/ai-standards-publictheir own version, first seen Nov 1, 2026
- ztc1522021381/github-repo-publishtheir own version, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- jgobuilds/ai-standards-public★ 0same name
- ztc1522021381/github-repo-publish★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- templates/copilot-instructions.mdCopilot instructions
- clean-code-concise-docsSkill
- data-analysis-explorerSkill
- data-science-workbenchSkill
- diff-reviewSkill
- distinctive-ui-designSkill
- domain-scaffoldingSkill
- git-commit-craftSkill
- laravel-web-studioSkill
- ml-model-engineeringSkill
- professional-report-writerSkill
- readme-github-syncSkill
- release-deploy-checkSkill
- security-auditSkill
- shadcn-admin-design-systemSkill
- verify-and-testSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 79
Commit awal chore: initialize repository dengan trailer co-author bila belum ada commit.
≈ “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
GitHub Repository Publish
Prosedur baku untuk menerbitkan repositori baru. Semua kewajiban ekosistem (nama berbahasa Inggris, trailer co-author, collaborator, topik) dijalankan dalam satu alur sehingga tidak ada yang terlewat.
Rule terkait: 08 (DevOps), 11.1 (Topics), 12 / 12.1 (Git dan Co-Authorship), 18 (Clean Handoff).
1. Prasyarat
gh auth status # wajib login
git config user.name # identitas commit terisi
git config user.emailJika gh auth status gagal, hentikan proses dan minta pengguna login. Jangan menyalin token secara manual ke perintah.
2. Aturan Penamaan
| Benar | Salah | Alasan |
indonesia-mutual-fund-analytics | reksadana-indonesia | Wajib bahasa Inggris |
clinic-queue-management | Clinic Queue | Tanpa spasi |
pos-cashier-system | pos_kasir_v2_final | Kebab-case, tanpa sufiks versi |
Nama berupa kebab-case huruf kecil, 2 sampai 5 kata, mendeskripsikan domain dan fungsi. Judul di README boleh Title Case (Indonesia Mutual Fund Analytics).
3. Pemeriksaan Sebelum Publish
Wajib lulus sebelum push pertama:
.gitignoremencakup:.env,.env.*(kecuali.env.example),node_modules/,vendor/,__pycache__/,.venv/,dist/,build/,*.log,.DS_Store.- Jalankan skill
diff-review(scan-diff.ps1 -All) untuk memastikan tidak ada secret, kredensial, atau data PII. - File berukuran di atas 50 MB tidak boleh di-commit; gunakan Git LFS atau keluarkan dari repo.
- README lulus
readme-github-sync/scripts/check-readme.ps1. - Form pre-filled dan bypass demo sudah dibersihkan (Rule 18), kecuali akun demo yang memang didokumentasikan di README.
4. Eksekusi Otomatis
powershell -ExecutionPolicy Bypass -File skills/github-repo-publish/scripts/publish-repo.ps1 `
-Name indonesia-mutual-fund-analytics `
-Description "Ranking and risk analytics for Indonesian mutual funds" `
-Visibility publicParameter:
| Parameter | Default | Fungsi |
-Name | wajib | Nama repo kebab-case berbahasa Inggris |
-Owner | pranataa-labs | Pemilik repo (user atau organisasi) |
-Description | kosong | Deskripsi singkat repo |
-Visibility | public | public atau private |
-Collaborator | ariasastra-dev | Akun yang diundang dengan izin push |
-DryRun | mati | Tampilkan langkah tanpa mengeksekusi |
Langkah yang dijalankan skrip:
- Validasi nama (kebab-case, ASCII).
git init -b mainbila belum ada repositori.- Commit awal
chore: initialize repositorydengan trailer co-author bila belum ada commit. gh repo create <owner>/<name> --source . --remote origin --push.- Undang collaborator:
gh api -X PUT repos/<owner>/<name>/collaborators/ariasastra-dev -f permission=push. - Sinkronisasi topik dari README melalui
readme-github-sync/scripts/sync-topics.ps1bila README tersedia.
5. Mengganti Nama Repositori
gh repo rename <nama-baru> --repo <owner>/<nama-lama> --yes
git remote set-url origin https://github.com/<owner>/<nama-baru>.gitSetelah rename: perbarui tautan di README, badge, package.json (repository, homepage), konfigurasi GitHub Pages (base di Vite), dan portofolio yang merujuk repo tersebut. GitHub membuat redirect otomatis, tetapi tautan tetap wajib diperbarui.
6. Alur Branch dan Pull Request
Untuk perubahan non-trivial setelah publish awal, gunakan branch dan PR agar riwayat dapat ditinjau:
git checkout -b feat/<ringkasan>
# ... commit atomik dengan trailer co-author ...
git push -u origin feat/<ringkasan>
gh pr create --fill --base main
gh pr merge --squash --delete-branch # hanya bila diotorisasi pengguna7. Checklist Laporan ke Pengguna
- URL repositori
- Status undangan collaborator (
ariasastra-dev) - Daftar topik yang tersinkron
- Hash commit awal
- URL GitHub Pages bila di-deploy
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.