Skip to content

feat: Copilot CLI skill parity with Claude integration #61

@bilersan

Description

@bilersan

Summary

The Copilot CLI integration currently has only 5 skills while Claude has 40. This creates a significant feature gap for Copilot CLI users who don't get the same context-aware assistance.

Problem

Integration Skills Hooks Governance
Claude 40 20+ Full
Copilot CLI 5 0 None

Proposed Solution

Port all 40 Claude skills to Copilot CLI format with:

  • YAML frontmatter using tools: [bash, read, write, edit, glob, grep] array format (vs Claude's allowed-tools string)
  • Lifecycle hook scripts (bash + PowerShell) for session-start/end and pre/post-tool-use
  • Agent bootstrap instructions (INSTRUCTIONS.md)
  • Hook configuration (ctx-hooks.json)

Skill Categories

Phase 1 - Core workflow: implement, commit, reflect, remember, wrap-up, brainstorm, spec
Phase 2 - Architecture & governance: architecture, consolidate, sanitize-permissions, prompt-audit, skill-audit, skill-creator
Phase 3 - Journal: journal-enrich, journal-enrich-all, journal-normalize
Phase 4 - Advanced: blog, blog-changelog, import-plans, loop, pause, resume, worktree
Phase 5 - Context management: add-convention, add-decision, add-learning, add-task, agent, archive, drift, prompt, recall, remind, status, verify, doctor
Internal: _ctx-alignment-audit

Infrastructure

  • 8 hook scripts (4 lifecycle events x bash + PowerShell)
  • INSTRUCTIONS.md agent bootstrap
  • ctx-hooks.json hook configuration
  • Updated embed.go for asset inclusion

Acceptance Criteria

  • All 40 Claude skills have Copilot CLI equivalents
  • Build passes with embedded assets
  • Lint clean (go vet + golangci-lint)
  • Compliance tests pass
  • Naming aligned 1:1 with Claude skills

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions