Create a CLI map topic for rapid publishing (#59413)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: hubwriter <hubwriter@github.com>

Author: 3 people

content/copilot/how-tos/configure-custom-instructions/add-repository-instructions.md

@@ -531,58 +531,6 @@ Whitespace between instructions is ignored, so the instructions can be written a
 
 <!-- end of Xcode tab -->
 
-<!-- START COPILOT CLI TAB -->
-
-{% copilotcli %}
-
-This version of this article is for using repository custom instructions with the {% data variables.product.prodname_copilot %} CLI. Click the tabs above for instructions on using custom instructions in other environments.
-
-## Creating custom instructions
-
-{% data variables.product.prodname_copilot %} supports three types of repository custom instructions.
-
-* **Repository-wide custom instructions**, which apply to all requests made in the context of a repository.
-
-  These are specified in a `copilot-instructions.md` file in the `.github` directory of the repository. See [Creating repository-wide custom instructions](#creating-repository-wide-custom-instructions).
-
-* **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
-
-  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions).
-
-  If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used. You should avoid potential conflicts between instructions as {% data variables.product.prodname_copilot_short %}'s choice between conflicting instructions is non-deterministic.
-
-* **Agent instructions** are used by AI agents.
-
-  {% data reusables.copilot.custom-instructions-agents %}
-
-  Alternatively, you can use a single `CLAUDE.md` or `GEMINI.md` file stored in the root of the repository.
-
-## Creating repository-wide custom instructions
-
-1. In the root of your repository, create a file named `.github/copilot-instructions.md`.
-
-   Create the `.github` directory if it does not already exist.
-
-1. Add natural language instructions to the file, in Markdown format.
-
-   Whitespace between instructions is ignored, so the instructions can be written as a single paragraph, each on a new line, or separated by blank lines for legibility.
-
-## Creating path-specific custom instructions
-
-{% data reusables.copilot.custom-instructions-path %}
-
-{% data reusables.copilot.custom-instructions-note %}
-
-## Further reading
-
-* [AUTOTITLE](/copilot/reference/custom-instructions-support)
-* [AUTOTITLE](/copilot/tutorials/customization-library/custom-instructions)—a curated collection of examples
-* [AUTOTITLE](/copilot/tutorials/use-custom-instructions)
-
-{% endcopilotcli %}
-
-<!-- end of Copilot CLI tab -->
-
 <!-- START ECLIPSE TAB -->
 
 {% eclipse %}

content/copilot/how-tos/copilot-cli/add-repository-instructions.md

@@ -0,0 +1,54 @@
+---
+title: Adding repository custom instructions
+shortTitle: Add repository instructions
+intro: 'Create repository custom instructions files that give {% data variables.product.prodname_copilot_short %} additional context on how to understand your project and how to build, test and validate its changes.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+contentType: how-tos
+---
+
+This version of this article is for using repository custom instructions with the {% data variables.product.prodname_copilot %} CLI. Click the tabs above for instructions on using custom instructions in other environments.
+
+## Creating custom instructions
+
+{% data variables.product.prodname_copilot %} supports three types of repository custom instructions.
+
+* **Repository-wide custom instructions**, which apply to all requests made in the context of a repository.
+
+  These are specified in a `copilot-instructions.md` file in the `.github` directory of the repository. See [Creating repository-wide custom instructions](#creating-repository-wide-custom-instructions).
+
+* **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
+
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions).
+
+  If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used. You should avoid potential conflicts between instructions as {% data variables.product.prodname_copilot_short %}'s choice between conflicting instructions is non-deterministic.
+
+* **Agent instructions** are used by AI agents.
+
+  {% data reusables.copilot.custom-instructions-agents %}
+
+  Alternatively, you can use a single `CLAUDE.md` or `GEMINI.md` file stored in the root of the repository.
+
+## Creating repository-wide custom instructions
+
+1. In the root of your repository, create a file named `.github/copilot-instructions.md`.
+
+   Create the `.github` directory if it does not already exist.
+
+1. Add natural language instructions to the file, in Markdown format.
+
+   Whitespace between instructions is ignored, so the instructions can be written as a single paragraph, each on a new line, or separated by blank lines for legibility.
+
+## Creating path-specific custom instructions
+
+{% data reusables.copilot.custom-instructions-path %}
+
+{% data reusables.copilot.custom-instructions-note %}
+
+## Further reading
+
+* [AUTOTITLE](/copilot/reference/custom-instructions-support)
+* [AUTOTITLE](/copilot/tutorials/customization-library/custom-instructions)—a curated collection of examples
+* [AUTOTITLE](/copilot/tutorials/use-custom-instructions)

content/copilot/how-tos/copilot-cli/index.md

@@ -0,0 +1,14 @@
+---
+title: GitHub Copilot CLI
+shortTitle: Copilot CLI
+intro: Learn how to use {% data variables.product.prodname_copilot %} in your terminal.
+versions:
+  feature: copilot
+children:
+  - /install-copilot-cli
+  - /add-repository-instructions
+  - /use-hooks
+  - /use-copilot-cli
+contentType: how-tos
+---
+

…ot/how-tos/set-up/install-copilot-cli.md …w-tos/copilot-cli/install-copilot-cli.mdcontent/copilot/how-tos/set-up/install-copilot-cli.md renamed to content/copilot/how-tos/copilot-cli/install-copilot-cli.md content/copilot/how-tos/set-up/install-copilot-cli.md renamed to content/copilot/how-tos/copilot-cli/install-copilot-cli.md

@@ -1,7 +1,7 @@
 ---
 title: Installing GitHub Copilot CLI
 shortTitle: Install Copilot CLI
-intro: 'Learn how to install {% data variables.copilot.copilot_cli_short %} so that you can use {% data variables.product.prodname_copilot_short %} directly from the command line.'
+intro: Learn how to install {% data variables.copilot.copilot_cli_short %} so that you can use {% data variables.product.prodname_copilot_short %} directly from the command line.
 versions:
   feature: copilot
 topics:
@@ -15,6 +15,7 @@ redirect_from:
   - /copilot/managing-copilot/configure-personal-settings/installing-github-copilot-in-the-cli
   - /copilot/how-tos/personal-settings/installing-github-copilot-in-the-cli
   - /copilot/how-tos/set-up/installing-github-copilot-in-the-cli
+  - /copilot/how-tos/set-up/install-copilot-cli
 contentType: how-tos
 category:
   - Configure Copilot

…os/use-copilot-agents/use-copilot-cli.md …t/how-tos/copilot-cli/use-copilot-cli.mdcontent/copilot/how-tos/use-copilot-agents/use-copilot-cli.md renamed to content/copilot/how-tos/copilot-cli/use-copilot-cli.md content/copilot/how-tos/use-copilot-agents/use-copilot-cli.md renamed to content/copilot/how-tos/copilot-cli/use-copilot-cli.md

@@ -5,6 +5,7 @@ intro: Learn how to use {% data variables.product.prodname_copilot %} from the c
 product: '{% data reusables.gated-features.copilot-cli %}'
 redirect_from:
   - /copilot/how-tos/use-copilot-cli
+  - /copilot/how-tos/use-copilot-agents/use-copilot-cli
 versions:
   feature: copilot
 topics:

content/copilot/how-tos/copilot-cli/use-hooks.md

@@ -0,0 +1,29 @@
+---
+title: Using hooks with GitHub Copilot CLI
+shortTitle: Use hooks
+intro: "Extend {% data variables.product.prodname_copilot %} agent behavior with custom shell commands at key points during agent execution."
+versions:
+  feature: copilot
+topics:
+  - Copilot
+contentType: how-tos
+category: 
+  - Configure Copilot
+---
+
+{% data reusables.copilot.coding-agent.hooks-intro %}
+
+## Creating a hook in a repository on {% data variables.product.github %}
+
+{% data reusables.copilot.coding-agent.create-hooks-instructions %}
+
+## Troubleshooting
+
+{% data reusables.copilot.coding-agent.troubleshoot-hooks %}
+
+## Further reading
+
+* [AUTOTITLE](/copilot/reference/hooks-configuration)
+* [AUTOTITLE](/copilot/concepts/agents/coding-agent/about-coding-agent)
+* [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli)
+* [AUTOTITLE](/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment)

content/copilot/how-tos/index.md

@@ -10,6 +10,7 @@ children:
   - /set-up
   - /get-code-suggestions
   - /chat-with-copilot
+  - /copilot-cli
   - /use-copilot-agents
   - /use-ai-models
   - /provide-context

content/copilot/how-tos/set-up/index.md

@@ -1,7 +1,7 @@
 ---
 title: Setting up GitHub Copilot
 shortTitle: Set up
-intro: 'Learn how to set up {% data variables.product.prodname_copilot %}.'
+intro: Learn how to set up {% data variables.product.prodname_copilot %}.
 topics:
   - Copilot
 versions:
@@ -12,9 +12,9 @@ children:
   - /set-up-for-enterprise
   - /set-up-a-dedicated-enterprise-for-copilot-business
   - /install-copilot-extension
-  - /install-copilot-cli
 redirect_from:
   - /copilot/setting-up-github-copilot
   - /copilot/get-started/setting-up-github-copilot
 contentType: how-tos
 ---
+

content/copilot/how-tos/use-copilot-agents/coding-agent/use-hooks.md

@@ -1,7 +1,7 @@
 ---
 title: Using hooks with GitHub Copilot agents
 shortTitle: Use hooks
-intro: 'Learn how to extend and customize {% data variables.product.prodname_copilot %} agent behavior by executing custom shell commands at key points during agent execution.'
+intro: 'Extend and customize {% data variables.product.prodname_copilot %} agent behavior by executing custom shell commands at key points during agent execution.'
 versions:
   feature: copilot
 topics:
@@ -11,101 +11,15 @@ category:
   - Configure Copilot
 ---
 
-Hooks allow you to extend and customize the behavior of {% data variables.product.prodname_copilot %} agents by executing custom shell commands at key points during agent execution. For a conceptual overview of hooks, see [AUTOTITLE](/copilot/concepts/agents/coding-agent/about-hooks).
+{% data reusables.copilot.coding-agent.hooks-intro %}
 
 ## Creating a hook in a repository on {% data variables.product.github %}
 
-1. Create a new `hooks.json` file with the name of your choice in the `.github/hooks/` folder of your repository. The hooks configuration file **must be present** on your repository's default branch to be used by {% data variables.copilot.copilot_coding_agent %}. For {% data variables.copilot.copilot_cli %}, hooks are loaded from your current working directory.
-
-1. In your text editor, copy and paste the following hook template. Remove any hooks you don't plan on using from the `hooks` array.
-
-    ```json copy
-    {
-      "version": 1,
-      "hooks": {
-        "sessionStart": [...],
-        "sessionEnd": [...],
-        "userPromptSubmitted": [...],
-        "preToolUse": [...],
-        "postToolUse": [...],
-        "errorOccurred": [...]
-      }
-    }
-    ```
-
-1. Configure your hook syntax under the `bash` or `powershell` keys, or directly reference script files you have created. 
-
-    * This example runs a script that outputs the start date of the session to a log file using the `sessionStart` hook:
-
-      ```json copy
-      "sessionStart": [
-        {
-          "type": "command",
-          "bash": "echo \"Session started: $(date)\" >> logs/session.log",
-          "powershell": "Add-Content -Path logs/session.log -Value \"Session started: $(Get-Date)\"",
-          "cwd": ".",
-          "timeoutSec": 10
-        }
-      ],
-      ```
-  
-    * This example calls out to an external `log-prompt` script:
-
-      ```json copy
-      "userPromptSubmitted": [
-        {
-          "type": "command",
-          "bash": "./scripts/log-prompt.sh",
-          "powershell": "./scripts/log-prompt.ps1",
-          "cwd": "scripts",
-          "env": {
-            "LOG_LEVEL": "INFO"
-          }
-        }
-      ],
-      ```
-
-      For a full reference on the input JSON from agent sessions along with sample scripts, see [AUTOTITLE](/copilot/reference/hooks-configuration).
-
-1. Commit the file to the repository and merge it into the default branch. Your hooks will now run during agent sessions.
+{% data reusables.copilot.coding-agent.create-hooks-instructions %}
 
 ## Troubleshooting
 
-If you run into problems using hooks, use the following table to troubleshoot.
-
-| Issue | Action |
-| --- | --- |
-| Hooks are not executing | <ul><li>Verify the JSON file is in the `.github/hooks/` directory.</li><li>Check for valid JSON syntax (for example, `jq .  hooks.json`).</li><li>Ensure `version: 1` is specified in your `hooks.json` file.</li><li>Verify the script you are calling from your hook is executable (`chmod +x script.sh`)</li><li>Check that the script has a proper shebang (for example, `#!/bin/bash`)</li></ul> |
-| Hooks are timing out | <ul><li>The default timeout is 30 seconds. Increase `timeoutSec` in the configuration if needed.</li><li>Optimize script performance by avoiding unnecessary operations.</li> |
-| Invalid JSON output | <ul><li>Ensure the output is on a single line.</li><li>On Unix, use `jq -c` to compact and validate the JSON output.</li><li>On Windows, use the `ConvertTo-Json -Compress` command in PowerShell to do the same.</li></ul> |
-
-## Debugging
-
-You can debug hooks using the following methods:
-
-* **Enable verbose logging** in the script to inspect the input data and trace script execution.
-
-  ```shell copy
-  #!/bin/bash
-  set -x  # Enable bash debug mode
-  INPUT=$(cat)
-  echo "DEBUG: Received input" >&2
-  echo "$INPUT" >&2
-  # ... rest of script
-  ```
-
-* **Test hooks locally** by piping test input into your hook to validate its behavior:
-
-  ```shell copy
-  # Create test input
-  echo '{"timestamp":1704614400000,"cwd":"/tmp","toolName":"bash","toolArgs":"{\"command\":\"ls\"}"}' | ./my-hook.sh
-
-  # Check exit code
-  echo $?
-
-  # Validate output is valid JSON
-  ./my-hook.sh | jq .
-  ```
+{% data reusables.copilot.coding-agent.troubleshoot-hooks %}
 
 ## Further reading
 

content/copilot/how-tos/use-copilot-agents/index.md

@@ -1,7 +1,7 @@
 ---
 title: Use GitHub Copilot agents
 shortTitle: Use Copilot agents
-intro: 'Learn how to use {% data variables.product.prodname_copilot %} agents.'
+intro: Learn how to use {% data variables.product.prodname_copilot %} agents.
 versions:
   feature: copilot
 topics:
@@ -10,9 +10,9 @@ children:
   - /manage-agents
   - /coding-agent
   - /request-a-code-review
-  - /use-copilot-cli
   - /copilot-memory
 redirect_from:
   - /copilot/how-tos/agents
 contentType: how-tos
 ---
+