github / github/copilot-cli

Feature Request: Argument auto-completion for skills / custom commands

Open
#4,812 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

Describe the feature or problem you'd like to solve

Skills can expose multiple parameters, but users currently need to remember them or look up the skill documentation before invocation. It would be useful for Copilot CLI to support PowerShell-style argument auto-completion for skills and custom commands.

Proposed solution

Proposed behavior

At minimum:

Auto-complete declared parameter names.
Support completion from partial parameter names.
Avoid suggesting already-used, non-repeatable parameters.
Derive completions directly from the skill's parameter/schema definition.

Optionally, parameter metadata could enable value completion:

file → filesystem completion
enum → allowed values
boolean → true / false
Why this is useful
Improves discoverability of skill capabilities.
Reduces typos and invalid arguments.
Avoids repeatedly checking skill documentation.
Makes parameter-rich skills feel like first-class CLI commands.
Lets skill authors define arguments once, with the CLI providing the completion experience automatically.

Example prompts or workflows

/deploy-service --environment --config <config.json>

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Copilot CLI completion entry point and the skill/custom command parameter or schema definition used for invocation. Trace how partial arguments are parsed, then verify that declared unused parameters are suggested and that optional value completion follows the stated metadata rules.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.