creating-instructions

Creates GitHub Copilot instruction files with scoped applyTo patterns and install-ready templates.

113|17|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill creating-instructions-jaktestowac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: creating-instructions
Source: https://github.com/jaktestowac/awesome-copilot-for-testers/tree/main/plugins/creating-instructions/skills/creating-instructions
Command: npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill creating-instructions-jaktestowac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing GitHub Copilot instructions often results in files that are too broad, too vague, or mixed with unrelated rules, causing Copilot to load irrelevant context or ignore conventions. This Skill turns repository conventions into clean, installable instruction files with the right scope and structure. ## Core Features & Use Cases - Instruction Type Selection: Decides between repo-wide copilot-instructions.md and scoped *.instructions.md files based on which files and audiences the rules affect. - Scoped Rule Authoring: Designs narrow applyTo glob patterns and writes short declarative rules with rationale and preferred/avoided code examples. - Templates and Quality Checklist: Ships repo-wide and scoped templates, worked examples, and a review checklist covering scope, rule quality, and separation of concerns. - Use Case: A team wants Copilot to follow Playwright fixture conventions only in their tests/ folder. The Skill produces a playwright-fixture.instructions.md file with applyTo: 'tests/**/*.{spec.ts,fixture.ts}', concrete rules, and code examples ready to commit. ## Quick Start Ask the assistant to create a scoped GitHub Copilot instructions file for your test folder that encodes your team's fixture and locator conventions.

Frequently Asked Questions about creating-instructions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub Copilot instructions file for my repository?▼

Create a copilot-instructions.md file describing your repository's purpose, stack, folder responsibilities, preferred commands, and implementation rules. Keep rules declarative and organized under headings so Copilot can find relevant guidance quickly.

What is the difference between copilot-instructions.md and .instructions.md files?▼

copilot-instructions.md applies repo-wide to nearly every task, while .instructions.md files use an applyTo glob pattern to target specific files, folders, or workflows. Use scoped files when rules only matter for part of the repository.

How do I choose the right applyTo pattern for Copilot instructions?▼

Choose an applyTo pattern narrow enough to cover only the files where the rules matter, such as 'tests/**/*.{spec.ts,fixture.ts}'. Avoid applyTo: '**' unless the guidance genuinely applies everywhere, since broad patterns load irrelevant context.

What should a good Copilot instruction file contain?▼

Include short declarative rules with rationale for non-obvious conventions, plus preferred and avoided code examples only where they improve compliance. Exclude agent personality, prompt workflows, step-by-step tutorials, and rules already enforced by linters or formatters.

Why is my Copilot instruction file being ignored or causing noise?▼

Common causes are an overly broad applyTo pattern, rules written as essays instead of declarative statements, or duplicated guidance across multiple files. Split unrelated audiences into separate scoped files and validate against a quality checklist.