{"meta":{"title":"Triage and summarize repository activity","intro":"Copilot can extract key information from repositories you follow to keep you up-to-date on recent activity.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/tutorials","title":"Tutorials"},{"href":"/en/copilot/tutorials/copilot-cookbook","title":"GitHub Copilot Cookbook"},{"href":"/en/copilot/tutorials/copilot-cookbook/communicate-effectively","title":"Communicate effectively"},{"href":"/en/copilot/tutorials/copilot-cookbook/communicate-effectively/summarize-repository-activity","title":"Summarize repository activity"}],"documentType":"article"},"body":"# Triage and summarize repository activity\n\nCopilot can extract key information from repositories you follow to keep you up-to-date on recent activity.\n\nGitHub Copilot CLI can help you summarize all recent activity in a repository. Copilot CLI will find information about issues, pull requests, commits, CI health, and security notifications, and you can ask it to summarize this information in a report for you.\n\n## Example scenario\n\nYou are returning to a repository after a week away and need to catch up. You want a single report that covers recent activity and the current health of the project so you can prioritize your work.\n\n## Example prompt\n\n```text copy\nSummarize activity in this repository over the past week. Highlight anything that looks blocked or urgent, and suggest what I should prioritize.\n```\n\n## Example response\n\n> \\[!NOTE] The following response is an example. Copilot Chat responses are non-deterministic, so you may get a different response from the one shown here.\n\n```text\nRepository activity summary (past 7 days)\n\nP1 — Urgent\n- CI failing on `main`: the `build-and-test` workflow has been red since commit a1b2c3d (\"Refactor auth middleware\"). Three subsequent PRs are blocked from merging.\n- Security alert: a high-severity Dependabot alert for `lodash` (CVE-2025-12345) is open and unassigned.\n\nP2 — Needs attention soon\n- PR #482 (\"Add OAuth device flow support\") has 2 approvals and passing checks, but has been waiting 4 days for a final sign-off from a code owner.\n- Issue #475 (\"Crash on startup with empty config file\") was reopened after a regression; 5 new comments and a reproduction case were added yesterday.\n\nP3 — Routine\n- 4 new issues opened, mostly minor UI bugs and documentation requests. None are labeled `bug:critical`.\n- 12 commits merged to `main` across 6 PRs, primarily dependency bumps and test cleanup.\n\nSuggested next steps:\n1. Investigate and fix the failing `build-and-test` workflow to unblock merges.\n2. Triage the Dependabot alert and assign an owner.\n3. Review PR #482 so it can ship.\n```\n\n## Further reading\n\n* [GitHub Copilot CLI](/en/copilot/how-tos/copilot-cli)"}