Skip to content

Add milestone-scope restriction to Copilot instructions #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Copilot wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add milestone-scope restriction to Copilot instructions #80

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5ced5f7
Initial plan
Copilot Feb 23, 2026
e4604f4
docs: add milestone-scope restriction to Copilot instructions
Copilot Feb 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,17 @@ JXLSwift is a native Swift implementation of the JPEG XL (ISO/IEC 18181) compres

---

## Scope of Work

> **You must only work on tasks that are explicitly defined in [`MILESTONES.md`](../MILESTONES.md).**

- **Do not** implement features, fix bugs, refactor code, add tests, or make any other changes that are not part of a milestone listed in `MILESTONES.md`.
- **Do not** add new milestones, deliverables, or acceptance criteria without explicit instruction from the project maintainer.
- Before starting any task, verify that it maps to an active (⬜ Not Started or 🔶 In Progress) milestone in `MILESTONES.md`.
- If a requested task falls outside the defined milestones, **stop and ask the maintainer** rather than proceeding.

---

## Unit Test Coverage

### Coverage Target: 95% and Above
Expand Down Expand Up @@ -181,6 +192,7 @@ Whenever a feature is added, modified, or removed, you **must** update the follo

When reviewing or generating code, verify:

- [ ] Task is part of an active milestone in `MILESTONES.md` (⬜ Not Started or 🔶 In Progress) — **do not proceed if it is not**.
- [ ] All public APIs have `///` documentation comments.
- [ ] Unit tests cover the new code with ≥ 95% branch coverage.
- [ ] Performance-sensitive code includes `measure {}` benchmarks.
Expand Down
11 changes: 11 additions & 0 deletions COPILOT_INSTRUCTIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,17 @@ The **public API must be backend-agnostic**. Consumers should never need to know

---

## Scope of Work

> **You must only work on tasks that are explicitly defined in [`MILESTONES.md`](MILESTONES.md).**

- **Do not** implement features, fix bugs, refactor code, add tests, or make any other changes that are not part of a milestone listed in `MILESTONES.md`.
- **Do not** add new milestones, deliverables, or acceptance criteria without explicit instruction from the project maintainer.
- Before starting any task, verify that it maps to an active (⬜ Not Started or 🔶 In Progress) milestone in `MILESTONES.md`.
- If a requested task falls outside the defined milestones, **stop and ask the maintainer** rather than proceeding.

---

## Architecture Rules

### No UI Frameworks in Core Targets
Expand Down