Assess publishing git-ape as a third-party agent in Awesome Copilot

[arnaudlh]

Goal

Assess and prepare the submission of git-ape as a third-party agent to github/awesome-copilot, following the guidelines in CONTRIBUTING.md.

Context

• Repository: Azure/git-ape
• Description: platform engineering framework for the agentic age
• License: MIT
• The submission target is the agents/ directory of github/awesome-copilot, contributed as a .agent.md file describing git-ape as a third-party agent.

Tasks

• Review the latest CONTRIBUTING.md for the third-party agent requirements (file naming, location, schema).
• Draft agents/git-ape.agent.md with required YAML frontmatter:
  • title
  • description (1–250 chars)
  • mcpServer (if applicable)
  • tags
  • authors
  • license (MIT)
  • source: https://github.com/Azure/git-ape
  • usage example
• Write agent documentation: purpose, main commands/capabilities, configuration, integration requirements.
• Confirm uniqueness — git-ape addresses a gap not covered by existing agents (platform engineering for the agentic age).
• Validate locally:
  • npm run collection:validate
  • npm start (ensure README/auto-generated files in sync, git diff clean)
• Ensure compliance with Responsible AI principles and security guidelines.
• Identify the primary maintainer/contact for the entry.
• Open a PR to github/awesome-copilot and link it back here.

Acceptance Criteria

• A feasibility assessment is documented in this issue (gaps, blockers, readiness).
• A draft git-ape.agent.md is prepared and reviewed.
• A submission PR is opened against github/awesome-copilot (or a clear reason is documented if not yet ready).

References

• Awesome Copilot CONTRIBUTING.md
• Awesome Copilot repository