GitHub Ops Skill

gh api

gh search

Overview

Map -> Identify -> Fetch

⚡ Essential Reconnaissance Commands

1. List Repository Root

gh api repos/{owner}/{repo}/contents --jq '.[].name'

2. List Specific Directory

gh api repos/{owner}/{repo}/contents/{path} --jq '.[].name'

3. Fetch File Content (Base64 Decoded)

gh api repos/{owner}/{repo}/contents/{path} --jq '.content' | base64 -d

4. Search for Pattern in Repository

gh search code "{pattern}" --repo {owner}/{repo}

5. Get Repository Metadata

gh repo view {owner}/{repo} --json description,stargazerCount,updatedAt

🔄 Token-Efficient Workflow

1. Map Tree: List the root and core directories (

   commands

   ,

   src

   ,

   docs

   ).
2. Identify Entrypoints: Look for

   README.md

   ,

   gemini-extension.json

   ,

   package.json

   , or

   SKILL.md

   .
3. Targeted Fetch: Download only the entrypoints first.
4. Deep Dive: Use

   gh search code

   to find logic patterns rather than reading every file.

🛡️ Platform Safety (Windows)

• When using

  base64 -d

  , ensure the output is redirected to a file using the

  Write

  tool if it's large.
• Avoid Linux-style

  /dev/stdin

  patterns in complex pipes.
• Use native paths for any local storage.

Assigned Agents

• artifact-integrator: Lead agent for repository onboarding.
• developer: PR management and exploration.

Memory Protocol (MANDATORY)

.claude/context/memory/learnings.md

• New pattern ->

  .claude/context/memory/learnings.md

• Issue found ->

  .claude/context/memory/issues.md

• Decision made ->

  .claude/context/memory/decisions.md

ASSUME INTERRUPTION: If it's not in memory, it didn't happen.