56 lines
1.6 KiB
Markdown
56 lines
1.6 KiB
Markdown
# Copilot Instructions
|
|
|
|
Read this file before starting any task. These rules apply to every task without exception.
|
|
|
|
---
|
|
|
|
## Environment
|
|
|
|
- `/workspace` is the project root and a git repo
|
|
- Use whatever language/runtime the project requires
|
|
- Never install packages globally unless the task explicitly asks
|
|
- Always verify installs work before reporting done
|
|
|
|
---
|
|
|
|
## Running Services
|
|
|
|
- Check if a service manager exists (systemd, start.sh, etc.) before starting anything manually
|
|
- Use `systemctl` if services are managed by systemd
|
|
- Check health after starting: `curl http://localhost:<port>/health` or equivalent
|
|
- Logs: `journalctl -u <service> -f` or check the project's log location
|
|
|
|
---
|
|
|
|
## Git
|
|
|
|
- `/workspace` is a git repo — use git for file tracking
|
|
- Use `git status --porcelain` to check changed files
|
|
- Use `git diff HEAD` for full diffs
|
|
- Never commit build artifacts, `__pycache__`, `*.pyc`, `node_modules`, or secrets
|
|
|
|
---
|
|
|
|
## Task Scope
|
|
|
|
- Do exactly what the task describes — nothing more, nothing less
|
|
- Do not add extra endpoints, files, dependencies, or features unless explicitly asked
|
|
- Do not refactor code from previous tasks unless asked
|
|
- If something seems wrong, flag it — don't silently fix it
|
|
|
|
---
|
|
|
|
## Verification
|
|
|
|
- Always run the verify command specified in the task before reporting done
|
|
- Report the exact output of the verify command
|
|
- If verification fails, fix the issue first — do not report partial completion
|
|
|
|
---
|
|
|
|
## Reporting Back
|
|
|
|
When a task is complete, report:
|
|
1. What was created or changed (file list)
|
|
2. The exact output of the verify command
|
|
3. Any assumptions made or issues encountered
|