Evaluate and maximize GitHub repo quality from 7/10 to 10/10 perfect
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Transform GitHub repos from good (7/10) to perfect (10/10) production-ready state.
Evaluate across 10 categories (0-10 each):
| Category | Weight | What to Check |
|---|---|---|
| Documentation | 10% | README completeness, examples, architecture docs |
| Installers/Setup | 10% | Automated setup, clear instructions, idempotent |
| Templates | 5% | Starter files, boilerplate, examples |
| CI/CD | 15% | GitHub Actions, automated testing, status badges |
| Examples | 5% | Screenshots, demos, video tutorials |
| Badges | 5% | CI, license, version, stars, forks |
| Changelog | 10% | CHANGELOG.md, semantic versioning, release notes |
| Releases | 10% | GitHub releases, tags, versioned artifacts |
| Issue Templates | 15% | Bug report, feature request, PR templates |
| Tests | 15% | Test suite, coverage, automated validation |
Scoring:
Total Score = Average of all categories
Create CHANGELOG.md
cat > CHANGELOG.md << 'EOF'
# Changelog
## [1.1.0] - YYYY-MM-DD
### Added
- Feature A
- Feature B
## [1.0.0] - YYYY-MM-DD
### Added
- Initial release
EOF
Create GitHub release
git tag -a v1.1.0 -m "v1.1.0 - Description"
git push origin v1.1.0
gh release create v1.1.0 --title "v1.1.0 - Title" --notes "Release notes"
Add badges to README
[](https://github.com/owner/repo/actions)
[](https://opensource.org/licenses/MIT)
[](https://github.com/owner/repo/releases)
[](https://github.com/owner/repo/stargazers)
[](https://github.com/owner/repo/network/members)
Add FAQ section (before Contributing)
## ❓ FAQ
### **Q: Common question 1?**
**A:** Clear answer with examples.
### **Q: Common question 2?**
**A:** Clear answer with code snippets.
[Add 8-10 questions based on user feedback]
Create GitHub Actions workflow
# .github/workflows/ci.yml
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: |
for script in *.sh; do
bash -n "$script"
done
- name: Validate documentation
run: |
test -f README.md || exit 1
test -f CHANGELOG.md || exit 1
test -f LICENSE || exit 1
- name: Run tests
run: |
if [ -f tests/test.sh ]; then
./tests/test.sh
fi
Create test suite
mkdir -p tests
cat > tests/test.sh << 'EOF'
#!/bin/bash
set -e
echo "=== Running Tests ==="
# Test 1: Syntax validation
echo "Test 1: Syntax validation..."
bash -n script.sh && echo "✅ Syntax OK" || exit 1
# Test 2: File existence
echo "Test 2: Required files..."
test -f README.md && echo "✅ README exists" || exit 1
# Test 3: Documentation completeness
echo "Test 3: Documentation..."
grep -q "Quick Start" README.md && echo "✅ Has Quick Start" || exit 1
echo "✅ ALL TESTS PASSED!"
EOF
chmod +x tests/test.sh
Verify CI passes
git add .github/workflows/ci.yml tests/
git commit -m "feat: add CI/CD and test suite"
git push
# Wait for CI to pass
gh run list --limit 1
Bug report template
mkdir -p .github/ISSUE_TEMPLATE
cat > .github/ISSUE_TEMPLATE/bug_report.md << 'EOF'
---
name: Bug report
about: Create a report to help us improve
title: '[BUG] '
labels: bug
---
## 🐛 Bug Description
Clear description of the bug.
## 📋 To Reproduce
Steps to reproduce:
1. Run command '...'
2. See error '...'
## ✅ Expected Behavior
What you expected to happen.
## 💻 Environment
- OS: [e.g. Ubuntu 24.04]
- Version: [e.g. 1.0.0]
## 🔍 Error Logs
Paste logs here
EOF
Feature request template
cat > .github/ISSUE_TEMPLATE/feature_request.md << 'EOF'
---
name: Feature request
about: Suggest an idea
title: '[FEATURE] '
labels: enhancement
---
## 🚀 Feature Description
Clear description of the feature.
## 💡 Motivation
Why is this needed?
## 📋 Proposed Solution
How should it work?
## ✅ Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
EOF
PR template
cat > .github/pull_request_template.md << 'EOF'
## 📋 Description
Brief description of changes.
## 🎯 Type of Change
- [ ] 🐛 Bug fix
- [ ] ✨ New feature
- [ ] 💥 Breaking change
- [ ] 📝 Documentation
## ✅ Checklist
- [ ] Code follows style guidelines
- [ ] Self-review completed
- [ ] Documentation updated
- [ ] Tests pass
EOF
--generate-notes for automatic changelog from commitsBefore (7/10):
After (10/10):
Time: 1.5 hours
Commits: 3 commits
Lines: 288 lines added
Result: Production-ready, world-class repo
Full case study: See references/mnemosyne-obsidian-case-study.md for detailed breakdown, lessons learned, and reusable patterns.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
中文简介正在准备中。当前显示原文说明。
Airtable REST API via curl. Records CRUD, filters, upserts.
中文简介正在准备中。当前显示原文说明。
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
中文简介正在准备中。当前显示原文说明。
Build monitoring bots that poll APIs and send notifications on state changes (new listings, price alerts, status updates)
中文简介正在准备中。当前显示原文说明。
REST/GraphQL API testing with automated validation — test endpoints, validate responses, check status codes, and ensure API contracts
中文简介正在准备中。当前显示原文说明。
Manage Apple Notes via memo CLI: create, search, edit.
中文简介正在准备中。当前显示原文说明。