opencode-manager
Copilot instructions912 starsChanged 3 days agoMITView on GitHub
We split this copilot-instructions.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Use of any type without justification
- Distinctive: line 19
Default exports (named exports only)
- Distinctive: line 43
All functions should have single responsibility
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Copilot Code Review Instructions
Technology Stack
- Monorepo: pnpm workspace with backend, frontend, and shared packages
- Backend: Bun runtime + Hono framework + Bun SQLite (bun:sqlite)
- Frontend: React 19 + Vite 7 + Radix UI + Tailwind CSS 4
- Validation: Zod schemas throughout
- State: React Query + Zustand
- Language: TypeScript (strict mode)
Code Style Requirements
Must Flag as Issues
- Inline, explanatory, or section comments (code must be self-documenting); JSDoc/TSDoc attached to the declaration it documents is allowed
- Console.log statements (use structured logging)
- Use of
anytype without justification - Default exports (named exports only)
- .then() chains (use async/await)
- Unused variables, imports, or dead code
- Direct state mutations in React components
Import Patterns
- Backend:
import { Hono } from 'hono' - Frontend:
import { Button } from '@/components/ui/button' - Shared types:
import { ... } from '@opencode-manager/shared'
Architecture Patterns
- Backend routes in
backend/src/routes/ - Backend services in
backend/src/services/ - Frontend pages in
frontend/src/pages/ - Shared types/schemas in
shared/src/
Quality Standards
- Test coverage: 80% minimum
- DRY: No duplicated logic
- SOLID principles enforced
- YAGNI: No speculative code
- All functions should have single responsibility
Review Focus Areas
- TypeScript type safety (no implicit any)
- Error handling with try/catch
- React hooks rules compliance
- Zod validation on API boundaries
- Consistent async/await usage
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.