메뉴
Sync a GitHub Project board into an emOS report grouped by status. Use when the user wants an up-to-date snapshot of a GitHub Projects (v2) board pulled into 10-reports/. Optionally pass a project number/URL, an owner, or a status filter as args.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create a new GitHub issue (optionally added to a GitHub Project board) following the project's standard format — gathers the details, shows a draft for confirmation, then creates it via the `gh` CLI. Use when the user wants to file, open, or create a GitHub issue. Optionally pass the repo and/or issue title as args.
Explore a remote GitHub repository read-only via the `gh` CLI — search code, read a file at a ref, view repo structure, trace the history/PRs touching a path, and blame lines. Use when investigating an incident or working an assignment against code you don't have checked out, across one or more repos. Pass the repo(s) (`owner/repo`) and what you're looking for as args.
Fetch a GitHub pull request as a structured bundle (metadata, diff, changed files with stats, commits, CI/check status, and existing review comments) via the `gh` CLI. Transport-only — it retrieves, it does not judge. Used by the tool-agnostic `pr-review` skill; you normally won't invoke it directly. Pass a PR number, URL, or branch (and optionally `owner/repo`) as args.
Do a first-line review pass on a pull request — summarize the changes, flag obvious issues, highlight architectural/dependency changes, and escalate what needs human attention. It hands you structured input to act on; it does NOT auto-approve or post to the code host. Use when the user wants a PR reviewed, triaged, or summarized before they dig in. Pass a PR number, URL, or branch as args.
Import any document by URL into emOS. Detects the transport (Confluence, Google Docs, GitHub, or a generic web page), delegates to the medium-specific provider skill when its capability is configured, classifies the content, files it, and pulls any action items assigned to the owner into the current week's plan. Use when the user gives a URL and wants its content brought into the vault. Pass the URL (and optionally a hint about the doc type) as args.
Create the planning file for the current week, carrying forward open TODOs and follow-ups from the previous week. Use when the user wants to start a new week's plan. No args needed.
| name | github-sync |
| description | Sync a GitHub Project board into an emOS report grouped by status. Use when the user wants an up-to-date snapshot of a GitHub Projects (v2) board pulled into 10-reports/. Optionally pass a project number/URL, an owner, or a status filter as args. |
Provider skill for the
issue_trackercapability (github) — thesync_iterationoperation. Active whenconfig.yaml→tools.issue_tracker: github. Adapter: .agents/integrations/github.md.
Snapshot a GitHub Projects (v2) board into emOS. This is the GitHub analog of jira-sync:
a board's columns play the role of a sprint's statuses.
Read GitHub settings from .agents/config.yaml → github: (project — the default board, a
number or URL) and external.github for link URLs.
gh CLI installed and authenticated. Reading a Project board needs the read:project
scope — if a command fails with missing required scopes [read:project], tell the user to run
gh auth refresh -s read:project and stop.Args (optional): a project number or URL, an owner (--owner), and/or a Projects
filter (e.g. -status:Done). Defaults:
github.project from config. If it's a URL it encodes the owner; if it's a bare
number you also need an owner.@me for a personal
board. Ask if ambiguous — don't guess.2026-W23).gh project field-list <number> --owner <owner> --format json
Status by default). Note
its key (the field name lowercased, e.g. status) for grouping in the next step.gh project item-list <number> --owner <owner> --format json --limit 200 [--query "<filter>"]
content (type = Issue | PullRequest | DraftIssue, plus title,
number, url, repository) and the board's field values flattened by lowercased field name
(e.g. status, assignees). Draft items have no url.To Do, In Progress, In Review, Done.10-reports/github-YYYY-Www.md:---
type: github-project-snapshot
week: YYYY-Www
date: YYYY-MM-DD
project: {board title or number}
projects: [] # emOS project slugs whose github_repo appears on this board (see step 5a)
---
## Board Snapshot — YYYY-Www
### In Progress
- [owner/repo#NNN](url) — Title — @Assignee
### In Review
- [owner/repo#NNN](url) — Title — @Assignee
### To Do
- [owner/repo#NNN](url) — Title — @Assignee
### Done
- [owner/repo#NNN](url) — Title — @Assignee
## Stats
- Total: N | Done: N | In Progress: N | To Do: N
[owner/repo#NNN](url) from content.repository + content.number +
content.url. For draft items (no url), show the title as plain text and mark (draft).5a. Link to emOS projects. Read the hub docs in 03-projects/*/ and collect any github_repo
values (the GitHub analog of jira_epic; format owner/repo). For any synced item whose
content.repository matches a hub's github_repo, add that project's {slug} to the
report's projects: frontmatter array and append a trailing #project/{slug} to that item's
line. The snapshot then surfaces in the linked projects' hubs on the next project-sync.
6. If a report for this week already exists, overwrite it.
7. Report: file path saved, item counts per status, linked project slugs, and any items flagged
#blocked or lacking an assignee.