You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Always consult the appropriate language-specific file when working with code in that language.
42
+
**Loaded Automatically on Demand**:
18
43
19
-
**Python Indentation Rule**: All Python code MUST use 2 spaces for indentation. This is enforced by `make indent-check` and is a hard requirement across the entire codebase.
44
+
-`testing.md` - Loaded when task involves tests or `test` keyword detected
45
+
-`javascript.md` - Loaded when `.js` files are being edited
46
+
-`shell.md` - Loaded when `.sh` files are being edited
47
+
-`makefile.md` - Loaded when Makefile or build system changes
48
+
49
+
Skills are detected and loaded based on file type, task keywords, and context signals. Explicitly request a skill if the auto-detection doesn't load it.
50
+
51
+
### Instruction Placement Policy (Critical)
52
+
53
+
- Prefer skill files under `.github/skills/` for detailed procedural rules.
54
+
- Keep this file focused on high-level routing and references to canonical skill documents.
55
+
- Avoid duplicating policy/checklist text across this file and skills.
56
+
- If overlap is found, retain one canonical source and replace duplicates with a short pointer.
20
57
21
58
## Architecture Overview
22
59
@@ -66,7 +103,7 @@ make rebuild-core # Clean + build (useful after code changes)
66
103
67
104
## Testing Framework
68
105
69
-
**For comprehensive test creation guidance, see `.github/instructions/testing.md`** - detailed instructions on creating unit, functional, integration, UI, and smoke tests with both positive and negative cases.
106
+
**For comprehensive test creation guidance, see `.github/skills/testing.md`** - detailed instructions on creating unit, functional, integration, UI, and smoke tests with both positive and negative cases.
70
107
71
108
**Running Tests** (must have containers running via docker-compose):
72
109
@@ -77,6 +114,20 @@ make -C tests unit-tests # Unit tests only
77
114
make -C tests geometry-unit # Specific test (e.g., geometry)
78
115
```
79
116
117
+
### Completion Gate For Test Tasks (Critical)
118
+
119
+
For runtime test verification requirements, use
120
+
`.github/skills/test-verification-gate.md`.
121
+
122
+
### Containerized Test Image Freshness Gate (Critical)
123
+
124
+
Use `.github/skills/test-verification-gate.md` as the single source of truth
125
+
for image freshness checks, rebuild-before-test requirements, and retry policy
126
+
for containerized test targets.
127
+
128
+
Service-specific examples belong in each service guide (for controller, see
-**`manager/secrets/`**: TLS certificates, auth tokens (never committed; generated per build)
168
219
-**`tests/Makefile`** and **`tests/Makefile.sscape`**: Test orchestration with Zephyr ID tracking
169
220
170
-
## Documentation Requirements
221
+
## Documentation Requirements (Always-On)
171
222
172
-
**ALWAYS read `.github/instructions/documentation.md` before making any code changes.** This file contains comprehensive documentation requirements and update procedures that must be followed for every agent request.
223
+
### WHEN to Update Documentation
224
+
225
+
**Update documentation IMMEDIATELY when making ANY of these changes:**
226
+
227
+
- Adding new features, services, models, or options
228
+
- Modifying APIs, endpoints, or request/response formats
229
+
- Changing build targets, Makefile commands, or deployment procedures
230
+
- Adding or removing configuration options or environment variables
231
+
- Updating dependencies or system requirements
232
+
- Changing default behaviors or conventions
233
+
234
+
### HOW to Update Documentation
235
+
236
+
**For detailed procedures, see `.github/skills/documentation-how.md`.**
237
+
238
+
This skill contains:
239
+
240
+
- Service-specific documentation locations (overview, build guides, API specs)
241
+
- Detailed update checklist per component
242
+
- Examples and patterns for each service type
243
+
- Cross-service documentation guidelines
244
+
245
+
**Quick reference - Key locations:**
246
+
247
+
-`docs/user-guide/microservices/<service>/<service>.md` - Features and API endpoints
description: "Reflect on this conversation and suggest instruction updates"
4
+
---
5
+
6
+
# Self-Reflection Task
7
+
8
+
## Instruction Placement Rule (Critical)
9
+
10
+
Before proposing documentation changes, apply this hierarchy:
11
+
12
+
1. Put detailed procedural policy in the most specific skill file under `.github/skills/`.
13
+
2. Keep `.github/copilot-instructions.md` as orchestration/entry-point guidance with pointers to skill files.
14
+
3. Keep `Agents.md` files service-specific with concrete examples and commands, not duplicated global policy text.
15
+
4. Do not duplicate the same checklist/policy text across global instructions and skill files.
16
+
5. If overlap is unavoidable, keep one canonical source and replace duplicates with short references.
17
+
18
+
6. Review the entire conversation history.
19
+
7. Identify patterns where I had to correct you or clarify my intent.
20
+
8. Suggest specific additions or modifications to the `.github/copilot-instructions.md`, files under `.github/skills` directory, `Agents.md` in each service directory and other relevant documentation to prevent these issues in the future.
21
+
9. Recommend any new 'Agent Skills', tools or prompts that would have made this task easier.
22
+
10. Provide the output as a set of actionable diffs or markdown blocks.
23
+
11. Explicitly identify any missed instruction and classify the root cause as:
24
+
- discovery failure
25
+
- execution failure
26
+
- verification failure
27
+
12. For test-related tasks, always include:
28
+
- the Makefile target that should have been run
29
+
- whether it was actually run
30
+
- the exact command and pass/fail summary (or the blocker)
0 commit comments