github-clippings-vp

GitHub Clippings VP

Use this skill to turn one or many GitHub URLs into structured raw-corpus cards under:

E:\LLM_wiki\LLM_wiki\01.raw\10.GitHub

The goal is not to create a bookmark list. The goal is to preserve GitHub material as engineering learning material: repository context, cases, code-reading notes, and reusable patterns.

Default Folder Scheme

Create missing folders when needed:

10.GitHub
├── 00.Index.md
├── 01.Repositories
├── 02.Cases
├── 03.CodeReading
├── 04.Patterns
└── 99.Archive

Use this routing for each URL independently:

• Repository URL -> 01.Repositories/owner__repo.md
• Pull request, issue, discussion, or commit URL -> 02.Cases/owner__repo__case-topic.md
• Source file, directory, symbol, or architecture-reading URL -> 03.CodeReading/owner__repo__module-or-topic.md
• Cross-case abstraction requested by the user -> 04.Patterns/pattern-topic.md
• Low-value, duplicate, or temporary material -> 99.Archive/

Do not create a separate PullRequests folder. PRs belong in 02.Cases because the durable value is the engineering case, not the GitHub object type.

Batch Input Rules

When the user provides multiple GitHub URLs:

1. Treat each URL as a separate source object, not as one combined article.
2. Parse and classify every URL before writing, then group by routed folder only for execution efficiency.
3. Create one Markdown card per URL unless the user explicitly asks to merge related URLs.
4. Preserve the original order in the final report and in 00.Index.md additions.
5. Deduplicate exact repeated URLs. If two URLs point to the same repo object with different anchors, keep the more specific URL as the source and mention the alternate anchor in the card.
6. Avoid overwriting existing files. If a filename already exists, update it only when it represents the same source URL; otherwise append a short suffix.
7. If some URLs fail to fetch, still process the successful URLs and report failed URLs separately.