repo-init
Initialize GitHub repo with CITATION.cff, LICENSE, README badges. Use for new repos.
What this skill does
# Repo Init
Sets up Hsieh-Ting Lin's standard public GitHub repository metadata: CITATION.cff, citation.bib, LICENSE, CSL files, README badges, and GitHub repo description.
## Quick Start
Run `/repo-init` in any repo root. The skill auto-detects:
- Repo name from git remote or directory name
- Primary language(s) from file extensions
- Existing README (preserves or creates)
## Workflow
```
- [ ] Step 1: Detect repo context (name, languages, description, existing files)
- [ ] Step 2: Create CITATION.cff
- [ ] Step 3: Create citation.bib
- [ ] Step 4: Create LICENSE (MIT)
- [ ] Step 5: Download AMA + APA CSL files to csl/
- [ ] Step 6: Create or update README.md with badges + citation block
- [ ] Step 7: Set gh repo description (if gh CLI available)
```
## Author (hardcoded)
```yaml
family-names: "Lin"
given-names: "Hsieh-Ting"
orcid: "https://orcid.org/0009-0002-3974-4528"
github: htlin222
```
## Step 1: Detect Repo Context
```bash
# Repo name
REPO_NAME=$(basename $(git rev-parse --show-toplevel 2>/dev/null || pwd))
# GitHub remote
GH_REMOTE=$(git remote get-url origin 2>/dev/null | sed 's|.*github.com[:/]||;s|\.git$||')
# e.g. "htlin222/survival-pipe"
# Primary languages (by file count)
# Check for: *.R, *.py, *.qmd, *.js, *.ts, *.go, *.rs, *.cpp, *.sh
```
Detect existing files — skip creating any that already exist (warn instead).
## Step 2: CITATION.cff
```yaml
cff-version: 1.2.0
message: "If you use this software, please cite it as below."
type: software
title: "{REPO_NAME}: {SHORT_DESCRIPTION}"
version: 0.1.0
date-released: "{CURRENT_YEAR}-01-01"
url: "https://github.com/htlin222/{REPO_NAME}"
repository-code: "https://github.com/htlin222/{REPO_NAME}"
license: MIT
authors:
- family-names: "Lin"
given-names: "Hsieh-Ting"
orcid: "https://orcid.org/0009-0002-3974-4528"
keywords:
- {auto-detect from repo content, 3-6 keywords}
abstract: >-
{One-sentence project description}
```
Ask the user for `SHORT_DESCRIPTION` and `abstract` if not obvious from existing README.
## Step 3: citation.bib
```bibtex
@software{lin{YEAR}{REPO_NAME_CLEAN},
author = {Lin, Hsieh-Ting},
title = {{REPO_NAME}: {SHORT_DESCRIPTION}},
year = {{YEAR}},
url = {https://github.com/htlin222/{REPO_NAME}},
version = {0.1.0}
}
```
Where `REPO_NAME_CLEAN` is the repo name with hyphens removed (e.g. `survivalpipe`).
## Step 4: LICENSE
Standard MIT License:
```
MIT License
Copyright (c) {YEAR} Hsieh-Ting Lin
Permission is hereby granted, free of charge, ...
```
## Step 5: CSL Files
Download to `csl/` directory:
```bash
mkdir -p csl
# AMA 11th edition
curl -sL "https://raw.githubusercontent.com/citation-style-language/styles/master/american-medical-association.csl" -o csl/american-medical-association.csl
# APA 7th edition
curl -sL "https://raw.githubusercontent.com/citation-style-language/styles/master/apa.csl" -o csl/apa.csl
```
If curl/WebFetch fails, create placeholder files with a comment noting the download URL.
## Step 6: README.md
### Badge Selection
Auto-select badges based on detected languages and features:
**Always include:**
- License badge: `[](LICENSE)`
- GitHub stars: `[](https://github.com/htlin222/{REPO}/stargazers)`
**If R detected (*.R, *.Rmd, renv.lock):**
- `[](https://www.r-project.org)`
**If Python detected (*.py, pyproject.toml, requirements.txt):**
- `[](https://www.python.org)`
**If Quarto detected (*.qmd, _quarto.yml):**
- `[](https://quarto.org)`
**If GitHub Pages / docs exist (pages/, docs/, .github/workflows/*pages*):**
- `[](https://htlin222.github.io/{REPO}/)`
**If GH Actions exist (.github/workflows/*.yml):**
- `[](https://github.com/htlin222/{REPO}/actions/workflows/{WORKFLOW}.yml)`
**If TypeScript/JavaScript (*.ts, *.js, package.json):**
- `[](https://www.typescriptlang.org)`
**If Go (*.go, go.mod):**
- `[](https://go.dev)`
**If Rust (*.rs, Cargo.toml):**
- `[](https://www.rust-lang.org)`
### README Structure
If README.md **doesn't exist**, create with full structure:
```markdown
{BADGES}
# {REPO_NAME}
{One-paragraph description}
## Quick Start
{Auto-detect: setup.sh, make, npm, pip, cargo, etc.}
## Citation
If you use this project, please cite it:
**BibTeX:**
```bibtex
{citation.bib content}
```
<details>
<summary>AMA format</summary>
Lin HT. {REPO_NAME}: {SHORT_DESCRIPTION}. Published online {YEAR}. https://github.com/htlin222/{REPO_NAME}
</details>
<details>
<summary>APA format</summary>
Lin, H.-T. ({YEAR}). *{REPO_NAME}: {SHORT_DESCRIPTION}* (Version 0.1.0) [Computer software]. https://github.com/htlin222/{REPO_NAME}
</details>
## License
This project is licensed under the [MIT License](LICENSE).
```
If README.md **already exists**, append or update only the missing sections (Citation, License, badges). Do NOT overwrite existing content. Insert badges at top if none exist.
## Step 7: GitHub Repo Description
If `gh` CLI is available and authenticated:
```bash
gh repo edit htlin222/{REPO_NAME} --description "{SHORT_DESCRIPTION}"
```
Ask user for confirmation before running this step.
## Post-Init Checklist
After completion, print:
```
Repo Init Complete:
[x] CITATION.cff
[x] citation.bib
[x] LICENSE (MIT)
[x] csl/american-medical-association.csl
[x] csl/apa.csl
[x] README.md (with badges + citation)
[ ] gh repo description (run: gh repo edit --description "...")
```
## Edge Cases
- **Monorepo**: If multiple languages detected, include all relevant badges
- **Existing LICENSE**: Warn and skip (don't overwrite a different license)
- **No git remote**: Use directory name, skip GH-specific steps
- **Private repo**: Skip stars badge, warn about Pages badge
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.