skills.rest
Ryokuman
RyokumanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

github-project-intake

Collects and verifies GitHub repository evidence for portfolio and project SSoT documentation.

1|Updated Jul 3, 2026
Search Tags:#github#portfolio#classification#gh cli#project documentation#evidence collection#repository inventory
One-click install
npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill github-project-intake-ryokuman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-project-intake
Source: https://github.com/Ryokuman/new_human_ochestrator/tree/main/system/20-skills/github-project-intake
Command: npx skills add https://github.com/Ryokuman/new_human_ochestrator --skill github-project-intake-ryokuman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Gathering accurate project information from GitHub accounts, organizations, and local repositories is error-prone: repos get missed, private data leaks into public documents, and unverified assumptions get written as facts. This Skill systematically inventories repositories, classifies them with the user, and produces verified evidence packs for portfolios or project SSoT records. ## Core Features & Use Cases - Repository Inventory & Classification: Enumerates repos across owners and organizations via the GitHub CLI, then presents them in batches of 10 for user decisions of apply, hold, or permanently exclude. - Project Bundling: Groups related FE, BE, API, docs, and infra repos under a title product project using verified linkage evidence rather than name similarity. - Evidence Pack Generation: Creates per-project README, architecture, issues, ownership, images, and metrics folders with confidence labels (verified, partially verified, inferred, needs confirmation). - Use Case: A developer preparing a portfolio connects their GitHub account, lets the Skill enumerate all personal and organization repos, classifies them interactively, and receives structured evidence folders with merged PR and commit references for each applied project. ## Quick Start Use the github-project-intake skill to survey my GitHub account and organizations, classify the repositories with me, and build verified evidence packs for the projects I approve.

Frequently Asked Questions about github-project-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory all my GitHub repositories including organizations?▼

Use gh repo list for each owner and gh api user/orgs to discover organizations you belong to. Record owner, visibility, primary language, and last push date for each repo, and mark inaccessible private repos as access-denied rather than missing.

How to gather project evidence from GitHub for a portfolio?▼

Combine remote GitHub data with local code inspection, then organize evidence into architecture, issues, ownership, and metrics folders. Prefer merged PRs, commit ranges, and code paths over vanity metrics like stars, and label every claim with a confidence level.

Can I switch GitHub CLI accounts for repo access?▼

Yes, run gh auth status to see logged-in accounts and gh auth switch -u <account> to change the active account. Failed authentication or insufficient permissions should be recorded as access-unavailable, not treated as missing repositories.

What should not be included when documenting private repos?▼

Never record token values from gh auth output, .env files, credentials, private keys, or production data. Sensitive private repo content should be abstracted into publicly shareable statements with evidence locations kept separate.

When should related repos be grouped into one project?▼

Group FE, BE, API, docs, and infra repos under a title product repo only when linkage is confirmed through README, package names, PRs, imports, or deployment docs. Similar names alone are not sufficient evidence for bundling.

Related Skills

Explore More Software Engineering Skills→
abonetoaboneto

speckit.git.remote

Parse GitHub owner and repository from git remote URLs.

Community
Intermediate
Chorus-AIDLCChorus-AIDLC
1.1k

release

Automate Chorus releases with CHANGELOG updates, version bumps, PRs, tags, and GitHub release notes.

Official
Intermediate
BryanPinheiro77BryanPinheiro77
2

env-secrets-manager

Scan repositories for leaked secrets and guide credential rotation workflows.

Community
Advanced
riftzen-bitriftzen-bit

ck

Manages per-project session state and generates context briefings via CLI.

Community
Advanced