sync-github-to-obsidian
Syncs markdown documentation from GitHub projects to Obsidian vault. Use when user wants to sync, export, or copy .md files from their code repositories to Obsidian for documentation browsing.
Syncs markdown documentation from GitHub projects to Obsidian vault. Use when user wants to sync, export, or copy .md files from their code repositories to Obsidian for documentation browsing.
Sync GitHub to Obsidian
Automatically extract and organize markdown documentation from GitHub projects into Obsidian vaults.
Configuration
Default paths (can be overridden by user):
- GitHub folder:
/Users/danieltang/GitHub - Obsidian vault:
~/Obsidian
Instructions
-
Scan the GitHub folder for project directories:
ls -la /Users/danieltang/GitHub -
For each project, find relevant .md files excluding:
node_modules/.git/lib/(dependency folders)target/(Rust build).changeset/(auto-generated changesets)
-
Create project folders in the Obsidian vault:
mkdir -p ~/Obsidian/PROJECT_NAME -
Copy .md files preserving directory structure:
find /Users/danieltang/GitHub/PROJECT_NAME -name "*.md" -type f \ -not -path "*/node_modules/*" \ -not -path "*/.git/*" \ -not -path "*/lib/*" \ -not -path "*/target/*" \ -not -path "*/.changeset/*" \ | while read f; do relpath="${f#/Users/danieltang/GitHub/PROJECT_NAME/}" dir=$(dirname "$relpath") mkdir -p ~/Obsidian/PROJECT_NAME/"$dir" cp "$f" ~/Obsidian/PROJECT_NAME/"$relpath" done -
Report summary with file counts per project
Options
When user requests sync, ask if they want to:
- Sync all projects or specific ones
- Clean existing folders first (full refresh) or merge
- Include or exclude
_legacy/and_archive/folders
Example Usage
User: "sync my github to obsidian"
User: "update obsidian with latest docs from github"
User: "export markdown from sooth-alpha to obsidian"
Output Format
Provide a summary table:
| Project | Files | Description |
|---|---|---|
| project-name | 42 | Brief description from README |
You Might Also Like
Related Skills
update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
vercel
docstring
Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
pytorch
docs-writer
Always use this skill when the task involves writing, reviewing, or editing files in the `/docs` directory or any `.md` files in the repository.
google-gemini
write-concept
Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines
leonardomsoresource-curator
Find, evaluate, and maintain high-quality external resources for JavaScript concept documentation, including auditing for broken and outdated links
leonardomso
doc-coauthoring
Guide 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.
anthropics