github-content
Fetch GitHub issues, PRs, repo contents, and code using the gh CLI. Use when the user shares GitHub URLs (issues, PRs, repos, source files) or asks about GitHub content. The gh CLI provides complete content that web fetching often misses due to JavaScript rendering.
What this skill does
# GitHub Content Fetching **When to activate:** - User pastes a GitHub URL (issue, PR, repo, or source file) - User asks about PR comments, reviews, or discussions - User wants to browse or search code in a GitHub repository - User references a GitHub issue or PR by number and repo **Why use gh CLI instead of web fetching:** GitHub's web interface relies heavily on JavaScript to load comments, reviews, and discussions. Web fetching often retrieves only partial content. The `gh` CLI accesses the API directly and returns complete data. ## Issues View an issue with all comments: ```bash gh issue view <number> --repo owner/repo --comments ``` ## Pull Requests View a PR with comments and review status: ```bash gh pr view <number> --repo owner/repo --comments ``` View the diff for a PR: ```bash gh pr diff <number> --repo owner/repo ``` View PR review comments (inline code comments): ```bash gh api repos/owner/repo/pulls/<number>/comments ``` List files changed in a PR: ```bash gh pr view <number> --repo owner/repo --json files --jq '.files[].path' ``` ## Repository Browsing List contents of a directory (defaults to root): ```bash gh api repos/owner/repo/contents/path/to/dir ``` View a specific file's contents: ```bash gh api repos/owner/repo/contents/path/to/file --jq '.content' | base64 -d ``` Get the full repository tree (all files): ```bash gh api repos/owner/repo/git/trees/main?recursive=1 --jq '.tree[] | select(.type=="blob") | .path' ``` Replace `main` with the appropriate branch name if needed. ## Code Search Search for code within a specific repository: ```bash gh search code "search query" --repo owner/repo ``` Search with language filter: ```bash gh search code "search query" --repo owner/repo --language python ``` Search with path filter: ```bash gh search code "search query" --repo owner/repo --path "src/" ``` View search results with more context: ```bash gh search code "search query" --repo owner/repo --json path,repository,textMatches ``` ## Parsing GitHub URLs Extract owner/repo from common URL patterns: | URL Pattern | Example | | ---------------------------------------- | ------------------------------- | | `github.com/owner/repo` | `github.com/zed-industries/zed` | | `github.com/owner/repo/issues/123` | Issue #123 in that repo | | `github.com/owner/repo/pull/456` | PR #456 in that repo | | `github.com/owner/repo/blob/branch/path` | Source file at path | | `github.com/owner/repo/tree/branch/path` | Directory at path | ## Tips - For large outputs, pipe through `head -n 100` or use `--jq` to filter - Use `--json` flag with `gh pr view` or `gh issue view` for structured data - For private repos, ensure `gh auth status` shows you're authenticated - When browsing files, the API returns base64-encoded content that needs decoding
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.