aboylabs/ai-agent-skills / skills/github/public-repo-creation
public-repo-creation
UnverifiedCreate production-ready public GitHub repositories with comprehensive documentation, automated setup, and quality assurance
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.1 KB |
| references/critical-bugs-mnemosyne-obsidian.md | markdown | 5.0 KB |
| references/deep-analysis-workflow.md | markdown | 5.7 KB |
| references/repo-maximization-checklist.md | markdown | 14.9 KB |
| references/setup-script-patterns.md | markdown | 11.6 KB |
references/repo-maximization-checklist.md
View on GitHub# Repository Quality Maximization Checklist
Complete checklist for transforming a good repo (7/10) into a perfect repo (10/10).
**Source:** mnemosyne-obsidian maximization session (2026-05-12)
---
## Scoring Framework
### Before (7/10 — Good)
- ✅ Good documentation
- ✅ Working installers
- ❌ No CI/CD
- ❌ No tests
- ❌ No issue templates
- ❌ No CHANGELOG
- ❌ No releases
- ❌ No FAQ
- ❌ Minimal badges
### After (10/10 — Perfect)
- ✅ Excellent documentation
- ✅ Tested installers
- ✅ CI/CD (GitHub Actions)
- ✅ Comprehensive test suite
- ✅ Issue templates (bug, feature)
- ✅ PR template
- ✅ CHANGELOG.md
- ✅ GitHub releases
- ✅ FAQ section
- ✅ 5+ badges
---
## Phase 1: CHANGELOG + Release (15 min)
### 1. Create CHANGELOG.md
```markdown
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [1.1.0] - 2026-05-12
### Added
- Feature X with smart detection
- Improvement Y for better UX
- Documentation Z
### Changed
- Updated README with comparison table
- Improved installer logic
### Fixed
- Bug A in edge case
- Issue B with error handling
## [1.0.0] - 2026-05-11
### Added
- Initial release
- Core features
- Documentation
- Setup script
```
### 2. Create Git Tag
```bash
git tag -a v1.1.0 -m "v1.1.0 - Feature Name"
git push origin v1.1.0
```
### 3. Create GitHub Release
```bash
gh release create v1.1.0 \
--title "v1.1.0 - Feature Name" \
--notes "## What's New
### Feature X
- Description
- Benefits
### Improvements
- Item 1
- Item 2
## Installation
\`\`\`bash
git clone https://github.com/user/repo.git
cd repo
./install.sh
\`\`\`
## Links
- [Full Changelog](https://github.com/user/repo/blob/main/CHANGELOG.md)
- [Documentation](https://github.com/user/repo#readme)"
```
---
## Phase 2: Badges + FAQ (20 min)
### 4. Add Badges to README
**Add at top of README.md:**
```markdown
[](https://github.com/user/repo/actions)
[](https://opensource.org/licenses/MIT)
[](https://github.com/user/repo/releases)
[](https://github.com/user/repo/stargazers)
[](https://github.com/user/repo/network/members)
```
### 5. Add FAQ Section
**Add before Contributing section in README.md:**
```markdown
## ❓ FAQ
### **Q: Common question 1?**
**A:** Detailed answer with examples.
### **Q: Common question 2?**
**A:** Detailed answer with code snippets if needed.
### **Q: Common question 3?**
**A:** Detailed answer with links to docs.
... (10+ questions total)
```
**Common FAQ topics:**
- Installation requirements
- Compatibility (OS, versions)
- Configuration options
- Troubleshooting common issues
- Feature usage
- Customization
- Updates and maintenance
- Security considerations
- Performance optimization
- Integration with other tools
---
## Phase 3: CI/CD + Tests (40 min)
### 6. Create GitHub Actions Workflow
**`.github/workflows/ci.yml`:**
```yaml
name: CI
on:
push:
branches: [ main ]
pull_request:
branches: [ main ]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Check Bash syntax
run: |
bash -n setup.sh
bash -n install.sh
- name: Validate documentation
run: |
test -f README.md || exit 1
test -f CHANGELOG.md || exit 1
test -f LICENSE || exit 1
test -f CONTRIBUTING.md || exit 1
echo "✅ All documentation files present"
- name: Check templates
run: |
test -d templates || exit 1
echo "✅ Templates directory exists"
- name: Run test suite
run: |
chmod +x tests/test-suite.sh
./tests/test-suite.sh
```
### 7. Create Test Suite
**`tests/test-suite.sh`:**
```bash
#!/bin/bash
set -e
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo "🧪 Testing Repository"
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo ""
# Test 1: Bash syntax validation
echo "📝 Test 1: Bash syntax validation..."
bash -n setup.sh && echo "✅ setup.sh syntax OK" || { echo "❌ setup.sh syntax error"; exit 1; }
bash -n install.sh && echo "✅ install.sh syntax OK" || { echo "❌ install.sh syntax error"; exit 1; }
echo ""
# Test 2: Required files exist
echo "📝 Test 2: Required files exist..."
test -f README.md && echo "✅ README.md exists" || { echo "❌ README.md missing"; exit 1; }
test -f CHANGELOG.md && echo "✅ CHANGELOG.md exists" || { echo "❌ CHANGELOG.md missing"; exit 1; }
test -f LICENSE && echo "✅ LICENSE exists" || { echo "❌ LICENSE missing"; exit 1; }
test -f CONTRIBUTING.md && echo "✅ CONTRIBUTING.md exists" || { echo "❌ CONTRIBUTING.md missing"; exit 1; }
echo ""
# Test 3: Templates exist
echo "📝 Test 3: Templates exist..."
test -d templates && echo "✅ templates/ directory exists" || { echo "❌ templates/ missing"; exit 1; }
echo ""
# Test 4: Documentation completeness
echo "📝 Test 4: Documentation completeness..."
grep -q "Quick Start" README.md && echo "✅ README has Quick Start" || { echo "❌ README missing Quick Start"; exit 1; }
grep -q "FAQ" README.md && echo "✅ README has FAQ" || { echo "❌ README missing FAQ"; exit 1; }
echo ""
# Test 5: Installers are executable
echo "📝 Test 5: Installers are executable..."
test -x setup.sh && echo "✅ setup.sh is executable" || { echo "❌ setup.sh not executable"; exit 1; }
echo ""
# Test 6: Custom tests (add your own)
echo "📝 Test 6: Custom validation..."
# Add project-specific tests here
echo "✅ Custom tests passed"
echo ""
# Summary
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo "✅ ALL TESTS PASSED!"
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
```
**Make executable:**
```bash
chmod +x tests/test-suite.sh
```
### 8. Verify CI Passes
```bash
# Push changes
git add .
git commit -m "feat: add CI/CD and test suite"
git push origin main
# Wait 10 seconds for CI to start
sleep 10
# Check CI status
gh run list --limit 1
```
---
## Phase 4: Issue Templates (15 min)
### 9. Bug Report Template
**`.github/ISSUE_TEMPLATE/bug_report.md`:**
```markdown
---
name: Bug report
about: Create a report to help us improve
title: '[BUG] '
labels: bug
assignees: ''
---
## 🐛 Bug Description
A clear and concise description of what the bug is.
## 📋 To Reproduce
Steps to reproduce the behavior:
1. Run command '...'
2. See error '...'
## ✅ Expected Behavior
A clear description of what you expected to happen.
## 📸 Screenshots
If applicable, add screenshots to help explain your problem.
## 💻 Environment
- **OS:** [e.g. Ubuntu 24.04, macOS 14]
- **Version:** [e.g. 1.0.0]
- **Other relevant info:** [e.g. Node.js version]
## 📝 Additional Context
Add any other context about the problem here.
## 🔍 Error Logs
```
Paste relevant error logs here
```
```
### 10. Feature Request Template
**`.github/ISSUE_TEMPLATE/feature_request.md`:**
```markdown
---
name: Feature request
about: Suggest an idea for this project
title: '[FEATURE] '
labels: enhancement
assignees: ''
---
## 🚀 Feature Description
A clear and concise description of the feature you'd like to see.
## 💡 Motivation
Why is this feature needed? What problem does it solve?
## 📋 Proposed Solution
Describe how you envision this feature working.
## 🔄 Alternatives Considered
Describe any alternative solutions or features you've considered.
## 📸 Mockups/Examples
If applicable, add mockups, diagrams, or examples.
## ✅ Acceptance Criteria
What would make this feature complete?
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
## 📝 Additional Context
Add any other context or screenshots about the feature request here.
```
### 11. PR Template
**`.github/pull_request_template.md`:**
```markdown
## 📋 Description
Brief description of what this PR does.
## 🎯 Type of Change
- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
- [ ] ✨ New feature (non-breaking change which adds functionality)
- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] 📝 Documentation update
- [ ] 🎨 Style/formatting changes
- [ ] ♻️ Code refactoring
- [ ] ⚡ Performance improvement
- [ ] ✅ Test updates
## 🧪 Testing
Describe the tests you ran to verify your changes:
- [ ] Tested locally
- [ ] Tested on fresh install
- [ ] Tested on existing setup
- [ ] All CI checks pass
## ✅ Checklist
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged and published
## 📸 Screenshots (if applicable)
Add screenshots to help explain your changes.
## 🔗 Related Issues
Closes #(issue number)
## 📝 Additional Notes
Any additional information that reviewers should know.
```
---
## Phase 5: Verification (10 min)
### 12. Run Test Suite Locally
```bash
./tests/test-suite.sh
```
**Expected output:**
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🧪 Testing Repository
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📝 Test 1: Bash syntax validation...
✅ setup.sh syntax OK
✅ install.sh syntax OK
📝 Test 2: Required files exist...
✅ README.md exists
✅ CHANGELOG.md exists
✅ LICENSE exists
✅ CONTRIBUTING.md exists
... (all tests)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ ALL TESTS PASSED!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
```
### 13. Check CI Status on GitHub
```bash
gh run list --limit 1
```
**Expected output:**
```
completed success feat: add CI/CD CI main push 12345678 30s 2026-05-12T12:34:56Z
```
### 14. Verify Badges Display
Visit GitHub repo page and check:
- ✅ CI badge shows "passing" (green)
- ✅ License badge shows "MIT"
- ✅ Version badge shows "v1.1.0"
- ✅ Stars badge shows count
- ✅ Forks badge shows count
### 15. Final Quality Score
**Checklist:**
- ✅ CI/CD: GitHub Actions passing
- ✅ Tests: 6+ tests passing
- ✅ Templates: Bug + feature + PR
- ✅ CHANGELOG: Semantic versioning
- ✅ Release: v1.1.0 published
- ✅ Badges: 5 badges
- ✅ FAQ: 10+ questions
- ✅ Documentation: Complete
**Score: 10/10 PERFECT** ✅
---
## Verification Commands
```bash
# 1. File count
find . -type f ! -path './.git/*' | wc -l
# 2. Repo size
du -sh . --exclude=.git
# 3. Run tests
./tests/test-suite.sh
# 4. CI status
gh run list --limit 1
# 5. Release info
gh release list
# 6. Check templates
ls -1 .github/ISSUE_TEMPLATE/ .github/pull_request_template.md
# 7. Verify CHANGELOG
cat CHANGELOG.md | head -20
# 8. Check badges (count)
grep -o 'img.shields.io' README.md | wc -l
```
---
## Common Pitfalls
### 1. CI Fails on First Run
**Problem:** Test suite has bugs or missing dependencies.
**Solution:**
- Test locally first: `./tests/test-suite.sh`
- Check CI logs: `gh run view`
- Fix issues and push again
### 2. Badges Don't Display
**Problem:** Wrong repo URL or workflow name.
**Solution:**
- Verify repo URL in badge markdown
- Check workflow name matches (case-sensitive)
- Wait 1-2 minutes for GitHub to update
### 3. Release Creation Fails
**Problem:** Tag already exists or gh CLI not authenticated.
**Solution:**
- Check existing tags: `git tag -l`
- Delete tag if needed: `git tag -d v1.0.0 && git push origin :refs/tags/v1.0.0`
- Re-authenticate: `gh auth login`
### 4. Tests Pass Locally But Fail in CI
**Problem:** Environment differences (paths, dependencies).
**Solution:**
- Use relative paths, not absolute
- Don't assume specific tools installed
- Mock external dependencies in tests
---
## Time Breakdown
| Phase | Tasks | Time |
|-------|-------|------|
| **Phase 1** | CHANGELOG + Release | 15 min |
| **Phase 2** | Badges + FAQ | 20 min |
| **Phase 3** | CI/CD + Tests | 40 min |
| **Phase 4** | Issue Templates | 15 min |
| **Phase 5** | Verification | 10 min |
| **Total** | | **1.5 hours** |
---
## Success Metrics
**Before (7/10):**
- 32/100 points
- Good but basic
- Missing automation
**After (10/10):**
- 80/100 points
- World-class quality
- Fully automated
- Production-ready
- Professional appearance
**Improvement:** +48 points (+150%)
---
## User Preference Notes
**From session (user: ryzen):**
- "gas maksimalkan" → Do full 10/10 transformation, not incremental
- "pastikan perfect" → Test everything, verify thoroughly
- Expects immediate action → No hesitation, execute workflow
- Wants comprehensive results → Production-ready excellence, not MVP
**Communication style:**
- "Mantap" / "Keren" / "Gas" = approval/confirmation
- Uses informal Indonesian
- Values speed + completeness
- Zero tolerance for errors
---
## Related Files
- [setup-script-patterns.md](setup-script-patterns.md) — Robust setup script patterns
- [critical-bugs-mnemosyne-obsidian.md](critical-bugs-mnemosyne-obsidian.md) — Common bugs to avoid
- [deep-analysis-workflow.md](deep-analysis-workflow.md) — Quality analysis framework
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |