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/critical-bugs-mnemosyne-obsidian.md
View on GitHub# Critical Bugs Found in mnemosyne-obsidian Repository
**Session:** 2026-05-12
**Repository:** https://github.com/kevinnft/mnemosyne-obsidian
**Context:** Creating production-ready public repo for Mnemosyne + Obsidian + GitHub Backup integration
## Bug #1: Token Duplication in ~/.bashrc
**Severity:** π΄ CRITICAL
**Impact:** Running setup.sh multiple times appends duplicate tokens to ~/.bashrc
### Problem Code
```bash
# setup.sh line 98 (BROKEN)
echo "export GH_TOKEN='$GITHUB_TOKEN'" >> ~/.bashrc
```
**What happens:**
- First run: Adds token to ~/.bashrc β
- Second run: Adds ANOTHER token to ~/.bashrc β
- After 10 runs: 10 duplicate tokens in ~/.bashrc β
### Root Cause
Using `>>` (append) without checking if entry already exists.
### Fix
```bash
# Only add to bashrc if not already present
if ! grep -q "export GH_TOKEN=" ~/.bashrc 2>/dev/null; then
echo "export GH_TOKEN='$GITHUB_TOKEN'" >> ~/.bashrc
echo "β
GitHub token saved to ~/.bashrc"
else
# Update existing token
sed -i "s|export GH_TOKEN=.*|export GH_TOKEN='$GITHUB_TOKEN'|" ~/.bashrc
echo "β
GitHub token updated in ~/.bashrc"
fi
```
**Key points:**
1. Check if pattern exists: `grep -q "export GH_TOKEN=" ~/.bashrc`
2. If not found: append new line
3. If found: update existing line with `sed -i`
4. Provide different feedback (saved vs updated)
### General Pattern
```bash
# Pattern for any config file
if ! grep -q "PATTERN" ~/.config 2>/dev/null; then
echo "NEW_LINE" >> ~/.config # Add new
else
sed -i "s|OLD_PATTERN|NEW_PATTERN|" ~/.config # Update existing
fi
```
**Use cases:**
- Adding environment variables to ~/.bashrc
- Adding aliases to ~/.bash_aliases
- Adding entries to ~/.ssh/config
- Adding lines to any config file that might be run multiple times
---
## Bug #2: Date Not Expanding in Heredoc
**Severity:** π‘ MEDIUM
**Impact:** Getting Started.md shows literal `$(date +%Y-%m-%d)` instead of actual date
### Problem Code
```bash
# setup.sh line 117-120 (BROKEN)
cat > "00 Meta/Getting Started.md" << 'EOF'
---
title: Getting Started
date: $(date +%Y-%m-%d)
tags:
- meta
- setup
---
EOF
```
**Output in file:**
```yaml
date: $(date +%Y-%m-%d) # β LITERAL STRING!
```
### Root Cause
Single-quoted heredoc delimiter (`<< 'EOF'`) prevents variable and command expansion.
**Bash heredoc rules:**
- `<< EOF` β Variables and commands expand
- `<< 'EOF'` β No expansion (literal)
- `<< "EOF"` β Variables expand, commands expand
### Fix
```bash
# Remove quotes from heredoc delimiter
cat > "00 Meta/Getting Started.md" << EOF
---
title: Getting Started
date: $(date +%Y-%m-%d)
tags:
- meta
- setup
---
# Getting Started
1. Open Obsidian: \`obsidian\` # Escape backticks!
2. Open this vault
3. Start creating notes!
EOF
```
**Output in file:**
```yaml
date: 2026-05-12 # β
ACTUAL DATE!
```
**Key points:**
1. Use `<< EOF` (no quotes) for expansion
2. Escape special characters that should be literal: `` \`backticks\` ``
3. Variables expand: `$HOME`, `$USER`, `$VAULT_PATH`
4. Commands expand: `$(date +%Y-%m-%d)`, `$(whoami)`
### When to Use Each
**Use `<< 'EOF'` (no expansion):**
- When content has many `$` or `` ` `` characters
- When writing shell scripts inside heredocs
- When you want literal `$VARIABLE` in output
**Use `<< EOF` (with expansion):**
- When you need current date/time
- When you need environment variables
- When you need computed values
**Example comparison:**
```bash
# No expansion (literal)
cat > script.sh << 'EOF'
#!/bin/bash
echo "User: $USER" # Will print: User: $USER
EOF
# With expansion
cat > config.txt << EOF
#!/bin/bash
echo "User: $USER" # Will print: User: ubuntu
EOF
```
### Escaping in Expanded Heredocs
When using `<< EOF` but need some literals:
```bash
cat > file.txt << EOF
# These expand:
Date: $(date +%Y-%m-%d)
User: $USER
# These are literal (escaped):
Price: \$100
Command: \`ls -la\`
Variable: \$HOME
EOF
```
**Output:**
```
Date: 2026-05-12
User: ubuntu
Price: $100
Command: `ls -la`
Variable: $HOME
```
---
## Testing & Prevention
### Syntax Check
```bash
bash -n setup.sh
# Should output nothing if syntax is valid
```
### Simulation Test
```bash
# Test date expansion
echo "Date: $(date +%Y-%m-%d)"
# Should output: Date: 2026-05-12
# Test heredoc expansion
cat << EOF
Date: $(date +%Y-%m-%d)
EOF
# Should output: Date: 2026-05-12
```
### Duplicate Prevention Test
```bash
# Run twice and check
./setup.sh # First run
grep -c "export GH_TOKEN=" ~/.bashrc # Should be 1
./setup.sh # Second run
grep -c "export GH_TOKEN=" ~/.bashrc # Should STILL be 1 (not 2!)
```
---
## Lessons Learned
1. **Always check before appending** to config files
2. **Use unquoted heredoc** (`<< EOF`) when you need expansion
3. **Test setup scripts** by running them multiple times
4. **Validate output** β check that dates/variables actually expanded
5. **Provide user feedback** β "saved" vs "updated" messages
---
## Related Patterns
See also:
- `setup-script-patterns.md` β More setup script best practices
- Skill: `public-repo-creation` β Full workflow for creating repos
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 |