From a4aebcd4bd354b59a6a6c12ab9c5c98a9d9e0276 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 1 Jul 2026 12:07:28 +1000 Subject: [PATCH] docs(learning-hub): add /pr auto, /pr automerge, and /chronicle skills review (#2168) Document three new CLI commands from Copilot CLI v1.0.66 (2026-06-30): - /pr auto: self-paced loop that fixes one failing item per run and paces around CI to drive a PR to green - /pr automerge: extends /pr auto to continue until the PR is fully merged (CI passes, reviews approved, PR merged) - /chronicle skills review: interactive review flow for agent-proposed draft skill changes (accept, reject, or defer each draft) Changes: - copilot-configuration-basics.md: add /pr auto + /pr automerge section in CLI Session Commands, extend /chronicle section with skills review subcommand - creating-effective-skills.md: add Q&A entry for /chronicle skills review in the Common Questions section Sources: - https://github.com/github/copilot-cli/commit/c802cc3f06ffd2a57968cf8efabd3d550650ac5e (changelog for v1.0.66) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Aaron Powell --- .../copilot-configuration-basics.md | 19 ++++++++++++++++++- .../learning-hub/creating-effective-skills.md | 12 +++++++++++- 2 files changed, 29 insertions(+), 2 deletions(-) diff --git a/website/src/content/docs/learning-hub/copilot-configuration-basics.md b/website/src/content/docs/learning-hub/copilot-configuration-basics.md index 86f88b5c..782eabba 100644 --- a/website/src/content/docs/learning-hub/copilot-configuration-basics.md +++ b/website/src/content/docs/learning-hub/copilot-configuration-basics.md @@ -3,7 +3,7 @@ title: 'Copilot Configuration Basics' description: 'Learn how to configure GitHub Copilot at user, workspace, and repository levels to optimize your AI-assisted development experience.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-06-29 +lastUpdated: 2026-06-30 estimatedReadingTime: '10 minutes' tags: - configuration @@ -533,6 +533,15 @@ The interval can be specified in seconds (`s`), minutes (`m`), or hours (`h`), a > **Note**: Scheduled prompts run in the background of the current session and use your active model. They share the session context window, so very frequent scheduling with long responses may consume context rapidly. Use `/compact` if context usage becomes a concern. +The `/pr auto` command *(v1.0.66+)* starts a self-paced automation loop that drives the current pull request to CI green. Rather than running continuously, it fixes one failing item per run and paces itself around CI checks to avoid redundant work: + +``` +/pr auto # start fixing the current PR until CI passes +/pr automerge # continue until the PR is fully merged +``` + +`/pr auto` is ideal when you have a PR with failing tests or linting errors — let it work through failures one at a time while you focus on other things. `/pr automerge` extends this further: it continues until all CI checks pass, required reviews are approved, and the PR is successfully merged. Both commands can be monitored and stopped from `/loop` or `/every`, which register the running automation as a scheduleable loop task. + The `/share html` command exports the current session — including conversation history and any research reports — as a **self-contained interactive HTML file**: ``` @@ -549,6 +558,14 @@ The `/chronicle` command opens an interactive timeline of everything the agent h Chronicle tracks which files were created, modified, or deleted during the session alongside the conversation that led to those changes. Use it to review what happened before a `/rewind`, audit what the agent changed, or share a summary of session activity with teammates. +The `/chronicle skills review` subcommand *(v1.0.66+)* opens an interactive review flow for proposed draft skill changes. When the agent has suggested additions or modifications to skills during a session, you can review each draft individually and choose to accept, reject, or defer: + +``` +/chronicle skills review +``` + +This keeps you in control of skill evolution — the agent can propose skill improvements as it discovers reusable patterns, but nothing is applied until you explicitly approve each change. + > **Note**: Session history, file tracking, and the `/chronicle` command were previously experimental features. As of v1.0.40, they are available to all users without enabling experimental mode. The `/diagnose` command (v1.0.64+) analyzes the current session's logs and surfaces diagnostic information to help troubleshoot unexpected behavior, performance issues, or errors: diff --git a/website/src/content/docs/learning-hub/creating-effective-skills.md b/website/src/content/docs/learning-hub/creating-effective-skills.md index b7beb05f..379ab599 100644 --- a/website/src/content/docs/learning-hub/creating-effective-skills.md +++ b/website/src/content/docs/learning-hub/creating-effective-skills.md @@ -3,7 +3,7 @@ title: 'Creating Effective Skills' description: 'Master the art of writing reusable, shareable skill folders that deliver consistent results across your team.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-06-25 +lastUpdated: 2026-06-30 estimatedReadingTime: '9 minutes' tags: - skills @@ -403,6 +403,16 @@ A: Yes, since v1.0.44. You can include multiple slash commands in a single messa A: Yes, for clarity. Show examples of desired output format, patterns to follow, or anti-patterns to avoid. For complex schemas or formats, consider bundling them as reference files rather than inline examples. +**Q: How do I review agent-proposed skill changes?** + +A: In v1.0.66+, the agent can propose draft skill additions or improvements as it discovers reusable patterns during a session. Review each draft interactively with: + +``` +/chronicle skills review +``` + +This opens a review flow where you can accept, reject, or defer each proposed change — giving you full control over how your skill library evolves. No changes are applied until you approve them. + ## Common Pitfalls to Avoid - ❌ **Vague description**: "Code helper" doesn't help agents discover the skill