Two files, one repository
j7-dev/everything-github-copilot ships 3 formats across 9 indexed files. The question worth asking is whether the second one says anything the first does not.
| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 13 | 9 | 0% |
| Commands | 0 | 0 | 4 | 0% |
| Section tags | 3 | 5 | 0 | 38% |
What each file covers
Sections
0 shared · 13 only in A · 9 only in B- − Everything Copilot CLI (ECC) — Agent Instructions
- − Core Principles
- − Available Agents
- − Agent Orchestration
- − Security Guidelines
- − Coding Style
- − Testing Requirements
- − Development Workflow
- − Git Workflow
- − Architecture Patterns
- − Performance
- − Project Structure
- − Success Metrics
- + CLAUDE.md
- + Project Overview
- + Running Tests
- + Run all tests
- + Run individual test files
- + Architecture
- + Key Commands
- + Development Notes
- + Contributing
Commands
0 shared · 0 only in A · 4 only in B- + node tests/run-all.js
- + node tests/lib/utils.test.js
- + node tests/lib/package-manager.test.js
- + node tests/hooks/hooks.test.js
Section tags
3 shared · 5 only in A · 0 only in B- − build
- − code-style
- − git-pr
- − security
- − performance
- test
- architecture
- agent-behaviour
Line diff
j7-dev/everything-github-copilot · AGENTS.md
@@ −1 @@
1# Everything Copilot CLI (ECC) — Agent Instructions
2
3This is a **production-ready AI coding plugin** providing 13 specialized agents, 50+ skills, 26 commands, and automated hook workflows for software development.
4
5## Core Principles
6
71. **Agent-First** — Delegate to specialized agents for domain tasks
82. **Test-Driven** — Write tests before implementation, 80%+ coverage required
93. **Security-First** — Never compromise on security; validate all inputs
104. **Immutability** — Always create new objects, never mutate existing ones
115. **Plan Before Execute** — Plan complex features before writing code
12
13## Available Agents
14
15| Agent | Purpose | When to Use |
16|-------|---------|-------------|
17| planner | Implementation planning | Complex features, refactoring |
18| architect | System design and scalability | Architectural decisions |
19| tdd-guide | Test-driven development | New features, bug fixes |
20| code-reviewer | Code quality and maintainability | After writing/modifying code |
21| security-reviewer | Vulnerability detection | Before commits, sensitive code |
22| build-error-resolver | Fix build/type errors | When build fails |
23| e2e-runner | End-to-end Playwright testing | Critical user flows |
24| refactor-cleaner | Dead code cleanup | Code maintenance |
25| doc-updater | Documentation and codemaps | Updating docs |
26| go-reviewer | Go code review | Go projects |
27| go-build-resolver | Go build errors | Go build failures |
28| database-reviewer | PostgreSQL/Supabase specialist | Schema design, query optimization |
29| python-reviewer | Python code review | Python projects |
30
31## Agent Orchestration
32
33Use agents proactively without user prompt:
34- Complex feature requests → **planner**
35- Code just written/modified → **code-reviewer**
36- Bug fix or new feature → **tdd-guide**
37- Architectural decision → **architect**
38- Security-sensitive code → **security-reviewer**
39
40Use parallel execution for independent operations — launch multiple agents simultaneously.
41
42## Security Guidelines
43
44**Before ANY commit:**
45- No hardcoded secrets (API keys, passwords, tokens)
46- All user inputs validated
47- SQL injection prevention (parameterized queries)
48- XSS prevention (sanitized HTML)
49- CSRF protection enabled
50- Authentication/authorization verified
51- Rate limiting on all endpoints
52- Error messages don't leak sensitive data
53
54**Secret management:** NEVER hardcode secrets. Use environment variables or a secret manager. Validate required secrets at startup. Rotate any exposed secrets immediately.
55
56**If security issue found:** STOP → use security-reviewer agent → fix CRITICAL issues → rotate exposed secrets → review codebase for similar issues.
57
58## Coding Style
59
60**Immutability (CRITICAL):** Always create new objects, never mutate. Return new copies with changes applied.
61
62**File organization:** Many small files over few large ones. 200-400 lines typical, 800 max. Organize by feature/domain, not by type. High cohesion, low coupling.
63
64**Error handling:** Handle errors at every level. Provide user-friendly messages in UI code. Log detailed context server-side. Never silently swallow errors.
65
66**Input validation:** Validate all user input at system boundaries. Use schema-based validation. Fail fast with clear messages. Never trust external data.
67
68**Code quality checklist:**
69- Functions small (<50 lines), files focused (<800 lines)
70- No deep nesting (>4 levels)
71- Proper error handling, no hardcoded values
72- Readable, well-named identifiers
73
74## Testing Requirements
75
76**Minimum coverage: 80%**
77
78Test types (all required):
791. **Unit tests** — Individual functions, utilities, components
802. **Integration tests** — API endpoints, database operations
813. **E2E tests** — Critical user flows
82
83**TDD workflow (mandatory):**
841. Write test first (RED) — test should FAIL
852. Write minimal implementation (GREEN) — test should PASS
863. Refactor (IMPROVE) — verify coverage 80%+
87
88Troubleshoot failures: check test isolation → verify mocks → fix implementation (not tests, unless tests are wrong).
89
90## Development Workflow
91
921. **Plan** — Use planner agent, identify dependencies and risks, break into phases
932. **TDD** — Use tdd-guide agent, write tests first, implement, refactor
943. **Review** — Use code-reviewer agent immediately, address CRITICAL/HIGH issues
954. **Commit** — Conventional commits format, comprehensive PR summaries
96
97## Git Workflow
98
99**Commit format:** `<type>: <description>` — Types: feat, fix, refactor, docs, test, chore, perf, ci
100
101**PR workflow:** Analyze full commit history → draft comprehensive summary → include test plan → push with `-u` flag.
102
103## Architecture Patterns
104
105**API response format:** Consistent envelope with success indicator, data payload, error message, and pagination metadata.
106
107**Repository pattern:** Encapsulate data access behind standard interface (findAll, findById, create, update, delete). Business logic depends on abstract interface, not storage mechanism.
108
109**Skeleton projects:** Search for battle-tested templates, evaluate with parallel agents (security, extensibility, relevance), clone best match, iterate within proven structure.
110
111## Performance
112
113**Context management:** Avoid last 20% of context window for large refactoring and multi-file features. Lower-sensitivity tasks (single edits, docs, simple fixes) tolerate higher utilization.
114
115**Build troubleshooting:** Use build-error-resolver agent → analyze errors → fix incrementally → verify after each fix.
116
117## Project Structure
118
119```
120agents/ — 13 specialized subagents (.agent.md)
121skills/ — 50+ workflow skills and domain knowledge
122commands/ — 26 slash commands
123hooks/ — Trigger-based automations (hooks.json)
124.github/ — Copilot instructions (copilot-instructions.md + *.instructions.md)
125scripts/ — Cross-platform Node.js utilities
126mcp-configs/ — 14 MCP server configurations
127tests/ — Test suite
128```
129
130## Success Metrics
131
132- All tests pass with 80%+ coverage
133- No security vulnerabilities
134- Code is readable and maintainable
135- Performance is acceptable
136- User requirements are met
137
j7-dev/everything-github-copilot · CLAUDE.md
@@ +1 @@
1# CLAUDE.md
2
3This file provides guidance to GitHub Copilot CLI when working with code in this repository.
4
5## Project Overview
6
7This is a **Copilot CLI plugin** - a collection of production-ready agents, skills, hooks, commands, rules, and MCP configurations. The project provides battle-tested workflows for software development using Copilot CLI.
8
9## Running Tests
10
11```bash
12# Run all tests
13node tests/run-all.js
14
15# Run individual test files
16node tests/lib/utils.test.js
17node tests/lib/package-manager.test.js
18node tests/hooks/hooks.test.js
19```
20
21## Architecture
22
23The project is organized into several core components:
24
25- **agents/** - Specialized subagents for delegation (planner, code-reviewer, tdd-guide, etc.)
26- **skills/** - Workflow definitions and domain knowledge (coding standards, patterns, testing)
27- **commands/** - Slash commands invoked by users (/tdd, /plan, /e2e, etc.)
28- **hooks/** - Trigger-based automations (session persistence, pre/post-tool hooks)
29- **rules/** - Always-follow guidelines (security, coding style, testing requirements)
30- **mcp-configs/** - MCP server configurations for external integrations
31- **scripts/** - Cross-platform Node.js utilities for hooks and setup
32- **tests/** - Test suite for scripts and utilities
33
34## Key Commands
35
36- `/tdd` - Test-driven development workflow
37- `/plan` - Implementation planning
38- `/e2e` - Generate and run E2E tests
39- `/code-review` - Quality review
40- `/build-fix` - Fix build errors
41- `/learn` - Extract patterns from sessions
42- `/skill-create` - Generate skills from git history
43
44## Development Notes
45
46- Package manager detection: npm, pnpm, yarn, bun (configurable via `PACKAGE_MANAGER` env var or project config)
47- Cross-platform: Windows, macOS, Linux support via Node.js scripts
48- Agent format: `.agent.md` with YAML frontmatter (name, description, tools) — no `model:` field
49- Skill format: Markdown with clear sections for when to use, how it works, examples
50- Hook format: `hooks.json` with `version: 1`, camelCase events, bash/powershell split
51
52## Contributing
53
54Follow the formats in CONTRIBUTING.md:
55- Agents: `.agent.md` with frontmatter (name, description, tools) — no `model:` field
56- Skills: Clear sections (When to Use, How It Works, Examples)
57- Commands: Markdown with description frontmatter
58- Hooks: `hooks/hooks.json` with `version: 1`, camelCase events
59
60File naming: agents use `agent-name.agent.md`; skills/commands use lowercase with hyphens
61
@@ −1 +1 @@
1−# Everything Copilot CLI (ECC) — Agent Instructions
1+# CLAUDE.md
22
3−This is a **production-ready AI coding plugin** providing 13 specialized agents, 50+ skills, 26 commands, and automated hook workflows for software development.
3+This file provides guidance to GitHub Copilot CLI when working with code in this repository.
44
5−## Core Principles
5+## Project Overview
66
7−1. **Agent-First** — Delegate to specialized agents for domain tasks
8−2. **Test-Driven** — Write tests before implementation, 80%+ coverage required
9−3. **Security-First** — Never compromise on security; validate all inputs
10−4. **Immutability** — Always create new objects, never mutate existing ones
11−5. **Plan Before Execute** — Plan complex features before writing code
7+This is a **Copilot CLI plugin** - a collection of production-ready agents, skills, hooks, commands, rules, and MCP configurations. The project provides battle-tested workflows for software development using Copilot CLI.
128
13−## Available Agents
9+## Running Tests
1410
15−| Agent | Purpose | When to Use |
16−|-------|---------|-------------|
17−| planner | Implementation planning | Complex features, refactoring |
18−| architect | System design and scalability | Architectural decisions |
19−| tdd-guide | Test-driven development | New features, bug fixes |
20−| code-reviewer | Code quality and maintainability | After writing/modifying code |
21−| security-reviewer | Vulnerability detection | Before commits, sensitive code |
22−| build-error-resolver | Fix build/type errors | When build fails |
23−| e2e-runner | End-to-end Playwright testing | Critical user flows |
24−| refactor-cleaner | Dead code cleanup | Code maintenance |
25−| doc-updater | Documentation and codemaps | Updating docs |
26−| go-reviewer | Go code review | Go projects |
27−| go-build-resolver | Go build errors | Go build failures |
28−| database-reviewer | PostgreSQL/Supabase specialist | Schema design, query optimization |
29−| python-reviewer | Python code review | Python projects |
11+```bash
12+# Run all tests
13+node tests/run-all.js
3014
31−## Agent Orchestration
15+# Run individual test files
16+node tests/lib/utils.test.js
17+node tests/lib/package-manager.test.js
18+node tests/hooks/hooks.test.js
19+```
3220
33−Use agents proactively without user prompt:
34−- Complex feature requests → **planner**
35−- Code just written/modified → **code-reviewer**
36−- Bug fix or new feature → **tdd-guide**
37−- Architectural decision → **architect**
38−- Security-sensitive code → **security-reviewer**
21+## Architecture
3922
40−Use parallel execution for independent operations — launch multiple agents simultaneously.
23+The project is organized into several core components:
4124
42−## Security Guidelines
25+- **agents/** - Specialized subagents for delegation (planner, code-reviewer, tdd-guide, etc.)
26+- **skills/** - Workflow definitions and domain knowledge (coding standards, patterns, testing)
27+- **commands/** - Slash commands invoked by users (/tdd, /plan, /e2e, etc.)
28+- **hooks/** - Trigger-based automations (session persistence, pre/post-tool hooks)
29+- **rules/** - Always-follow guidelines (security, coding style, testing requirements)
30+- **mcp-configs/** - MCP server configurations for external integrations
31+- **scripts/** - Cross-platform Node.js utilities for hooks and setup
32+- **tests/** - Test suite for scripts and utilities
4333
44−**Before ANY commit:**
45−- No hardcoded secrets (API keys, passwords, tokens)
46−- All user inputs validated
47−- SQL injection prevention (parameterized queries)
48−- XSS prevention (sanitized HTML)
49−- CSRF protection enabled
50−- Authentication/authorization verified
51−- Rate limiting on all endpoints
52−- Error messages don't leak sensitive data
34+## Key Commands
5335
54−**Secret management:** NEVER hardcode secrets. Use environment variables or a secret manager. Validate required secrets at startup. Rotate any exposed secrets immediately.
36+- `/tdd` - Test-driven development workflow
37+- `/plan` - Implementation planning
38+- `/e2e` - Generate and run E2E tests
39+- `/code-review` - Quality review
40+- `/build-fix` - Fix build errors
41+- `/learn` - Extract patterns from sessions
42+- `/skill-create` - Generate skills from git history
5543
56−**If security issue found:** STOP → use security-reviewer agent → fix CRITICAL issues → rotate exposed secrets → review codebase for similar issues.
44+## Development Notes
5745
58−## Coding Style
46+- Package manager detection: npm, pnpm, yarn, bun (configurable via `PACKAGE_MANAGER` env var or project config)
47+- Cross-platform: Windows, macOS, Linux support via Node.js scripts
48+- Agent format: `.agent.md` with YAML frontmatter (name, description, tools) — no `model:` field
49+- Skill format: Markdown with clear sections for when to use, how it works, examples
50+- Hook format: `hooks.json` with `version: 1`, camelCase events, bash/powershell split
5951
60−**Immutability (CRITICAL):** Always create new objects, never mutate. Return new copies with changes applied.
52+## Contributing
6153
62−**File organization:** Many small files over few large ones. 200-400 lines typical, 800 max. Organize by feature/domain, not by type. High cohesion, low coupling.
54+Follow the formats in CONTRIBUTING.md:
55+- Agents: `.agent.md` with frontmatter (name, description, tools) — no `model:` field
56+- Skills: Clear sections (When to Use, How It Works, Examples)
57+- Commands: Markdown with description frontmatter
58+- Hooks: `hooks/hooks.json` with `version: 1`, camelCase events
6359
64−**Error handling:** Handle errors at every level. Provide user-friendly messages in UI code. Log detailed context server-side. Never silently swallow errors.
65−
66−**Input validation:** Validate all user input at system boundaries. Use schema-based validation. Fail fast with clear messages. Never trust external data.
67−
68−**Code quality checklist:**
69−- Functions small (<50 lines), files focused (<800 lines)
70−- No deep nesting (>4 levels)
71−- Proper error handling, no hardcoded values
72−- Readable, well-named identifiers
73−
74−## Testing Requirements
75−
76−**Minimum coverage: 80%**
77−
78−Test types (all required):
79−1. **Unit tests** — Individual functions, utilities, components
80−2. **Integration tests** — API endpoints, database operations
81−3. **E2E tests** — Critical user flows
82−
83−**TDD workflow (mandatory):**
84−1. Write test first (RED) — test should FAIL
85−2. Write minimal implementation (GREEN) — test should PASS
86−3. Refactor (IMPROVE) — verify coverage 80%+
87−
88−Troubleshoot failures: check test isolation → verify mocks → fix implementation (not tests, unless tests are wrong).
89−
90−## Development Workflow
91−
92−1. **Plan** — Use planner agent, identify dependencies and risks, break into phases
93−2. **TDD** — Use tdd-guide agent, write tests first, implement, refactor
94−3. **Review** — Use code-reviewer agent immediately, address CRITICAL/HIGH issues
95−4. **Commit** — Conventional commits format, comprehensive PR summaries
96−
97−## Git Workflow
98−
99−**Commit format:** `<type>: <description>` — Types: feat, fix, refactor, docs, test, chore, perf, ci
100−
101−**PR workflow:** Analyze full commit history → draft comprehensive summary → include test plan → push with `-u` flag.
102−
103−## Architecture Patterns
104−
105−**API response format:** Consistent envelope with success indicator, data payload, error message, and pagination metadata.
106−
107−**Repository pattern:** Encapsulate data access behind standard interface (findAll, findById, create, update, delete). Business logic depends on abstract interface, not storage mechanism.
108−
109−**Skeleton projects:** Search for battle-tested templates, evaluate with parallel agents (security, extensibility, relevance), clone best match, iterate within proven structure.
110−
111−## Performance
112−
113−**Context management:** Avoid last 20% of context window for large refactoring and multi-file features. Lower-sensitivity tasks (single edits, docs, simple fixes) tolerate higher utilization.
114−
115−**Build troubleshooting:** Use build-error-resolver agent → analyze errors → fix incrementally → verify after each fix.
116−
117−## Project Structure
118−
119−```
120−agents/ — 13 specialized subagents (.agent.md)
121−skills/ — 50+ workflow skills and domain knowledge
122−commands/ — 26 slash commands
123−hooks/ — Trigger-based automations (hooks.json)
124−.github/ — Copilot instructions (copilot-instructions.md + *.instructions.md)
125−scripts/ — Cross-platform Node.js utilities
126−mcp-configs/ — 14 MCP server configurations
127−tests/ — Test suite
128−```
129−
130−## Success Metrics
131−
132−- All tests pass with 80%+ coverage
133−- No security vulnerabilities
134−- Code is readable and maintainable
135−- Performance is acceptable
136−- User requirements are met
60+File naming: agents use `agent-name.agent.md`; skills/commands use lowercase with hyphens
13761
