What problem does it solve? Writing GitHub Copilot prompt files that actually work requires knowing the current VS Code prompt schema, valid frontmatter fields, input placeholder syntax, and tool selection rules. This Skill guides the creation, review, and debugging of .prompt.md files so slash commands are discoverable, inputs are consumed, and tools follow least privilege. ## Core Features & Use Cases - Prompt File Authoring: Produces .github/prompts/<name>.prompt.md files with correct frontmatter (name, description, argument-hint, agent, model, tools) and ordered task contracts using ${input:name:placeholder} variables. - Schema-Grounded Review: Inspects the active VS Code prompt schema and available agent/tool identifiers before writing, avoiding hardcoded or undocumented tool identifiers. - Verification Workflow: Validates YAML parsing, unique names, consumed inputs, resolvable links, and behavior with complete, missing, and malformed inputs. - Use Case: A developer repeatedly runs the same read-only code review. Use this Skill to create a /review-boundary slash command that takes a path input, restricts tools to search, and reports defects with file evidence without editing files. ## Quick Start Create a GitHub Copilot prompt file for a repeatable review task with defined inputs, allowed tools, and verification steps.
