بنقرة واحدة
github
// Interact with GitHub (issues, PRs, repos, releases) using the `gh` CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.
// Interact with GitHub (issues, PRs, repos, releases) using the `gh` CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.
Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
Use this skill when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user. Trigger on: 'write me a brief', 'one-pager', 'memo', 'data sheet', 'status matrix', 'short deck', 'summary deck', 'closing slide', 'final deliverable'. Routes to `officecli merge` with one of three pre-built starter templates that already carry the Commonly palette, fonts, and structure — so you populate content with one merge call instead of 30 individual `officecli set` commands. DO NOT use for fundraising decks (use `officecli-pitch-deck`), academic papers (use `officecli-academic-paper`), or financial models (use `officecli-financial-model`).
Convert binary documents (PDF, DOCX, XLSX, PPTX, HTML, EPUB, images) to clean LLM-friendly Markdown using Microsoft's `markitdown` Python tool. Use when a user attaches a binary file and you need to read its contents.
Convert Markdown to PDF (or DOCX/EPUB/HTML) using the `pandoc` CLI. Use when asked to produce a PDF report, brief, summary, or any document where the input is Markdown and the output should be a polished, paginated file.
Manipulate PDF files — extract text, count pages, render thumbnails, merge or split documents. Use for PDF-specific operations that don't fit `markdown-converter` (general read) or `pandic-office` (write from markdown).
Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).
| name | github |
| description | Interact with GitHub (issues, PRs, repos, releases) using the `gh` CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc. |
gh CLIThe gh CLI is installed on PATH. The gateway environment provides a
GITHUB_PAT env var (a Team-Commonly fine-grained PAT with repo + PR scope)
which gh picks up automatically as GH_TOKEN.
The active GitHub identity is Team-Commonly bot identity — anything you push, comment, or open will be attributed to that account.
# List open issues in a repo
gh issue list --repo Team-Commonly/commonly --state open
# Create an issue
gh issue create --repo Team-Commonly/commonly \
--title "Title here" \
--body "Body here"
# Comment on an issue
gh issue comment 123 --repo Team-Commonly/commonly --body "comment"
# List open PRs
gh pr list --repo Team-Commonly/commonly --state open
# View a PR (diff, comments, status)
gh pr view 287 --repo Team-Commonly/commonly --json title,body,additions,deletions
# Get a PR's diff
gh pr diff 287 --repo Team-Commonly/commonly
# Comment on a PR
gh pr comment 287 --repo Team-Commonly/commonly --body "comment text"
# Check CI status
gh pr checks 287 --repo Team-Commonly/commonly
# View a file at a specific ref
gh api repos/Team-Commonly/commonly/contents/README.md --jq '.content' | base64 -d
# Search code
gh search code 'commonly_attach_file' --repo Team-Commonly/commonly --limit 20
# List recent workflow runs
gh run list --repo Team-Commonly/commonly --limit 10
# View a specific run's logs
gh run view 12345 --repo Team-Commonly/commonly --log
gh pr comment 287 --repo Team-Commonly/commonly --body "$(cat <<'EOF'
Multi-line comment.
- Bullet one
- Bullet two
EOF
)"
--repo <org/name> explicitly; the gateway's working
directory may not be inside a clone.--json <fields> --jq <expr> over scraping plain output —
more reliable and structured.gh pr create --base main --head <branch>" and let humans review.sam-local-codex via DM
(per ADR-005 Stage 3).