luigidemasi opened a new issue, #71:
URL: https://github.com/apache/camel-kit/issues/71

   > Imported from 
[luigidemasi/camel-kit#129](https://github.com/luigidemasi/camel-kit/issues/129),
 opened by [luigidemasi](https://github.com/luigidemasi) on 2026-07-04.
   > Closed by 
[luigidemasi/camel-kit#130](https://github.com/luigidemasi/camel-kit/pull/130), 
merged on 2026-07-05.
   
   ---
   
   ## Summary
   
   Add first-class GitHub Copilot CLI support to Camel Kit so users can run:
   
   ```bash
   camel-kit init --ai copilot
   ```
   
   The target should generate Copilot-native repository assets for 
instructions, skills, custom agents, and guardrails, using the current 
`copilot` CLI from `@github/copilot`.
   
   ## Rationale
   
   GitHub Copilot CLI now supports repository custom instructions, project 
skills, project custom agents, hooks, MCP servers, programmatic prompt mode, 
sandboxing, permission allow/deny rules, and built-in review/security/research 
agents. Camel Kit can use those surfaces to expose its Camel workflow more 
directly than a generic `AGENTS.md` export.
   
   ## Proposed Output
   
   Generate Copilot assets such as:
   
   - `.github/copilot-instructions.md`
   - `.github/mcp.json`
   - `.github/skills/...`
   - `.github/agents/*.agent.md`
   - `.github/hooks/*.json` after hook behavior is tested
   - Copilot setup docs for MCP and safe permissions
   
   Use `.github/mcp.json` for committed Copilot CLI workspace MCP 
configuration. Do not emit `.vscode/mcp.json`; VS Code and Copilot CLI use 
separate MCP configuration surfaces.
   
   ## Acceptance Criteria
   
   - `camel-kit init --ai copilot` is accepted by the CLI.
   - A `copilot` agent descriptor is added to the agent registry.
   - A Copilot-specific generator creates Copilot-native repository files.
   - Generated instructions include Camel Kit workflow, build/test commands, 
artifact expectations, MCP usage rules, and validation guidance.
   - Generated project skills are discoverable by Copilot CLI under 
`.github/skills`.
   - Generated custom agents are discoverable under `.github/agents`.
   - Generated MCP servers are configured under `.github/mcp.json` and visible 
through `copilot mcp list --json` or `/mcp show`.
   - Security guidance avoids `--yolo` and `--allow-all` except in isolated 
sandboxes.
   - Docs explain safe `--allow-tool` and `--deny-tool` examples.
   - Docs explain how to configure Camel Kit MCP servers for Copilot CLI.
   - Tests cover registry discovery, generator output, shipped templates, and 
init service behavior.
   
   ## Security Requirements
   
   - Use least-privilege tool recommendations.
   - Deny `git push` in automation examples.
   - Deny broad destructive shell operations in recommended hooks.
   - Do not rely on trusted directories or local sandbox host filtering as the 
only security control.
   - Do not enable transcript sharing by default.
   - Mark installed-version MCP loading behavior, Copilot MCP policy behavior, 
and Java LSP details as implementation-time verification items.
   
   ## References
   
   - https://docs.github.com/en/copilot/how-tos/copilot-cli
   - 
https://docs.github.com/en/copilot/concepts/agents/copilot-cli/about-copilot-cli
   - 
https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-command-reference
   - 
https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions
   - 
https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-skills
   - 
https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/create-custom-agents-for-cli
   - 
https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers
   - https://docs.github.com/en/copilot/reference/hooks-reference
   - 
https://docs.github.com/en/copilot/how-tos/cloud-and-local-sandboxes/configuring-local-sandbox-settings


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to