context-mode 1.0.53 → 1.0.56

package/skills/context-mode-ops/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: context-mode-ops
+description: Manage context-mode GitHub issues, PRs, and releases with parallel subagent army. Orchestrates 10-20 dynamic agents (Architects, Staff Engineers, QA) per task. Use when triaging issues, reviewing PRs, releasing versions, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
+---
+
+# Context Mode Ops
+
+Parallel subagent army for issue triage, PR review, and releases.
+
+## TDD-First: BLOCKING GATE
+
+<tdd_enforcement>
+STOP. Before writing ANY implementation code, you MUST have a failing test.
+No exceptions. No "I'll add tests later." No "this change is too small for tests."
+This codebase has 12 adapters, 3 OS, hooks, FTS5, sessions — it is FRAGILE.
+One untested change breaks everything. TDD is not optional, it is the gate.
+</tdd_enforcement>
+
+**Read [tdd.md](tdd.md) FIRST. It is the law.** Summary:
+
+1. **STOP** if you haven't written a failing test. You cannot write implementation code.
+2. **Vertical slices ONLY**: ONE test → ONE implementation → repeat. NEVER all tests first.
+3. **Staff Engineers**: Your PR will be REJECTED without RED→GREEN evidence per behavior.
+4. **Architects**: REJECT any change without tests. No exceptions, no "trivial change" excuse.
+5. **QA Engineer**: Run full suite after EVERY change. Report failures immediately.
+
+## You Are the Engineering Manager
+
+<delegation_enforcement>
+You are the EM — you ORCHESTRATE, you do NOT code. You MUST delegate ALL work to subagents.
+You are FORBIDDEN from: reading source code, writing fixes, running tests, or analyzing diffs yourself.
+Your ONLY job: spawn agents, route results, make ship/no-ship decisions.
+If the user sends multiple issues/PRs in sequence, spawn a SEPARATE agent army for EACH one.
+Never fall back to doing the work yourself. If an agent fails, spawn another agent — not yourself.
+</delegation_enforcement>
+
+For every task:
+
+1. **Analyze** — Read the issue/PR with `gh` (via agent), classify affected domains
+2. **Recruit** — Spawn domain-specific agent teams from [agent-teams.md](agent-teams.md)
+3. **Dispatch** — ALL agents in ONE parallel batch (10-20 agents minimum)
+4. **Ping-pong** — Route Architect reviews ↔ Staff Engineer fixes
+5. **Ship** — Push to `next`, comment, close
+
+## Workflow Detection
+
+| User says | Workflow | Reference |
+|-----------|----------|-----------|
+| "triage issue #N", "fix issue", "analyze issue" | Triage | [triage-issue.md](triage-issue.md) |
+| "review PR #N", "merge PR", "check PR" | Review | [review-pr.md](review-pr.md) |
+| "release", "version bump", "publish" | Release | [release.md](release.md) |
+
+## GitHub CLI (`gh`) Is Mandatory
+
+<gh_enforcement>
+ALL GitHub operations MUST use the `gh` CLI. Never use raw git commands for GitHub interactions.
+Never use curl/wget to GitHub API. `gh` handles auth, pagination, and rate limits correctly.
+</gh_enforcement>
+
+- `gh issue view`, `gh issue comment`, `gh issue close` — for issues
+- `gh pr view`, `gh pr diff`, `gh pr merge --squash`, `gh pr edit --base next` — for PRs
+- `gh release create` — for releases
+
+## Agent Spawning Protocol
+
+1. Read issue/PR body + comments + diff via `gh` (through agent)
+2. Identify affected: adapters, OS, core modules
+3. Build agent roster from [agent-teams.md](agent-teams.md) — context-driven, not static
+4. Spawn ALL agents in ONE message with multiple `Agent` tool calls
+5. Every code-changing agent gets `isolation: "worktree"`
+6. Use context-mode MCP tools inside agents for large output
+
+## Validation (Every Workflow)
+
+Before shipping ANY change, validate per [validation.md](validation.md):
+- [ ] ENV vars verified against real platform source (not LLM hallucinations)
+- [ ] All 12 adapter tests pass: `npx vitest run tests/adapters/`
+- [ ] TypeScript compiles: `npm run typecheck`
+- [ ] Full test suite: `npm test`
+- [ ] Cross-OS path handling checked
+
+## Docs Must Stay Current
+
+After ANY code change that affects adapters, features, or platform support:
+- [ ] Update `docs/platform-support.md` if adapter capabilities changed
+- [ ] Update `README.md` if install instructions, features, or platform list changed
+- [ ] These updates are NOT optional — ship docs with code, not after
+
+## Communication (Every Workflow)
+
+Follow [communication.md](communication.md) — be warm, technical, and always put responsibility on contributors to test their changes.
+
+## Cross-Cutting References
+
+- [TDD Methodology](tdd.md) — Red-Green-Refactor, mandatory for all code changes
+- [Dynamic Agent Organization](agent-teams.md)
+- [Validation Patterns](validation.md)
+- [Communication Templates](communication.md)
+
+## Installation
+
+```shell
+# Install via skills CLI
+npx skills add mksglu/context-mode --skill context-mode-ops
+
+# Or install all context-mode skills
+npx skills add mksglu/context-mode
+
+# Or direct path
+npx skills add https://github.com/mksglu/context-mode/tree/main/skills/context-mode-ops
+```

package/skills/context-mode-ops/agent-teams.md

@@ -0,0 +1,198 @@
+# Dynamic Agent Organization
+
+## Principle: Context-Driven Teams
+
+Every issue and PR gets a **custom** team. Agents are spawned based on what the task touches — never a static roster. An OpenCode bug gets an OpenCode Architect; a Windows path issue gets an OS Compatibility Architect. A single task may spawn 10-20 agents.
+
+## Engineering Manager Protocol
+
+You (the main conversation) are the EM. You **ORCHESTRATE ONLY** — you NEVER do the work yourself.
+
+<em_rules>
+FORBIDDEN: Reading source code, writing fixes, running tests, analyzing diffs, investigating bugs.
+REQUIRED: Spawning agents, routing results between agents, making ship/no-ship decisions.
+If user sends multiple issues/PRs: spawn a SEPARATE agent army for EACH. Never queue them.
+If an agent fails: spawn a replacement agent. NEVER fall back to doing it yourself.
+</em_rules>
+
+Your loop:
+
+```
+1. CLASSIFY  → Read issue/PR via agent, identify affected domains
+2. RECRUIT   → Build agent roster from tables below
+3. DISPATCH  → Spawn ALL agents in ONE message (parallel)
+4. MONITOR   → Read agent results as they complete
+5. PING-PONG → Route architect feedback to staff engineers
+6. VALIDATE  → All architects must APPROVE before shipping
+7. SHIP      → Merge, comment, close
+```
+
+**Critical**: Never spawn agents one at a time. Always ONE message, multiple `Agent` tool calls.
+
+## Agent Roster
+
+### Core Agents (Always Spawned)
+
+| Agent | Role | When |
+|-------|------|------|
+| **Context Mode Architect** | Reviews ALL changes against core architecture. Validates FTS5, MCP protocol, session continuity. Final approval gate. | Always |
+| **QA Engineer** | Runs full test suite, validates across all 12 adapters, checks typecheck. Reports pass/fail matrix. | Always |
+| **DX Engineer** | Reviews user-facing output quality. Checks error messages, help text, diagnostic output. | Always |
+
+### Platform Agents (Spawned When Platform Is Affected)
+
+Spawn the **pair** (Architect + Staff Engineer) for each affected platform:
+
+| Platform | Architect Prompt | Staff Engineer Prompt |
+|----------|-----------------|----------------------|
+| **Claude Code** | "You are the Claude Code Architect. Review changes to `src/adapters/claude-code/`, hooks, plugin.json, marketplace.json. Validate CLAUDE_PROJECT_DIR and CLAUDE_SESSION_ID env handling." | "You are the Claude Code Staff Engineer. Implement fixes in the claude-code adapter. Run `npx vitest run tests/adapters/claude-code.test.ts`." |
+| **Gemini CLI** | "You are the Gemini CLI Architect. Review `src/adapters/gemini-cli/`, BeforeTool/AfterTool hook format, settings.json schema. Validate GEMINI_PROJECT_DIR and GEMINI_CLI env handling." | "You are the Gemini CLI Staff Engineer. Implement fixes in the gemini-cli adapter. Run `npx vitest run tests/adapters/gemini-cli.test.ts`." |
+| **OpenCode** | "You are the OpenCode Architect. Review `src/adapters/opencode/`, AGENTS.md injection, config paths. Validate OPENCODE and OPENCODE_PID env handling." | "You are the OpenCode Staff Engineer. Implement fixes in the opencode adapter. Run `npx vitest run tests/adapters/opencode.test.ts`." |
+| **OpenClaw** | "You are the OpenClaw Architect. Review `src/adapters/openclaw/`, openclaw.plugin.json, thinking block handling. Validate OPENCLAW_HOME and OPENCLAW_CLI env handling." | "You are the OpenClaw Staff Engineer. Implement fixes in the openclaw adapter. Run `npx vitest run tests/adapters/openclaw.test.ts` and `tests/plugins/openclaw.test.ts`." |
+| **Kilo** | "You are the Kilo Architect. Review `src/adapters/kilo/`, config at `~/.config/kilo/`. Validate KILO and KILO_PID env handling." | "You are the Kilo Staff Engineer. Implement fixes in the kilo adapter. Run `npx vitest run tests/adapters/kilo.test.ts`." |
+| **Codex** | "You are the Codex Architect. Review `src/adapters/codex/`. Validate CODEX_CI and CODEX_THREAD_ID env handling." | "You are the Codex Staff Engineer. Implement fixes in the codex adapter. Run `npx vitest run tests/adapters/codex.test.ts`." |
+| **VS Code Copilot** | "You are the VS Code Copilot Architect. Review `src/adapters/vscode-copilot/`, `.vscode/mcp.json` format, `.github/hooks/` structure. Validate VSCODE_PID and VSCODE_CWD env handling." | "You are the VS Code Copilot Staff Engineer. Implement fixes. Run `npx vitest run tests/adapters/vscode-copilot.test.ts`." |
+| **Cursor** | "You are the Cursor Architect. Review `src/adapters/cursor/`, `.cursor/mcp.json` format. Validate CURSOR_TRACE_ID and CURSOR_CLI env handling." | "You are the Cursor Staff Engineer. Implement fixes. Run `npx vitest run tests/adapters/cursor.test.ts`." |
+| **Antigravity** | "You are the Antigravity Architect. Review `src/adapters/antigravity/`." | "You are the Antigravity Staff Engineer. Implement fixes. Run `npx vitest run tests/adapters/antigravity.test.ts`." |
+| **Kiro** | "You are the Kiro Architect. Review `src/adapters/kiro/`, `~/.kiro/` config." | "You are the Kiro Staff Engineer. Implement fixes. Run `npx vitest run tests/adapters/kiro.test.ts`." |
+| **Pi** | "You are the Pi Architect. Review `src/adapters/pi/`, `.pi/extensions/` structure." | "You are the Pi Staff Engineer. Implement fixes. Run `npx vitest run tests/adapters/pi.test.ts`." |
+| **Zed** | "You are the Zed Architect. Review `src/adapters/zed/`, `~/.config/zed/` settings." | "You are the Zed Staff Engineer. Implement fixes. Run `npx vitest run tests/adapters/zed.test.ts`." |
+
+### Domain Agents (Spawned When Domain Is Affected)
+
+| Trigger Keywords | Agent | Focus |
+|-----------------|-------|-------|
+| FTS5, SQLite, better-sqlite3, `.db`, native binding | **Database Architect** | FTS5 schema, WAL mode, native bindings across OS, `better-sqlite3` build |
+| Security, bypass, injection, file-writing, sandbox escape | **Security Engineer** | Sandbox boundaries, file write restrictions, path traversal, command injection |
+| Windows, path separator, `\\`, WSL, Git Bash, `process.platform` | **OS Compatibility Architect** | Cross-platform paths, temp dirs, native bindings per OS |
+| macOS + specific issue | **macOS Staff Engineer** | Homebrew paths, `.dylib` bindings, Gatekeeper |
+| Linux + specific issue | **Linux Staff Engineer** | Snap/PATH limitations, `.so` bindings, CI envs |
+| Windows + specific issue | **Windows Staff Engineer** | Path separators, native bindings, PowerShell vs Git Bash |
+| Hook, PreToolUse, PostToolUse, SessionStart, PreCompact | **Hooks Architect** | Hook lifecycle, matcher patterns, stdin/stdout protocol |
+| Session, compaction, resume, snapshot, continuity | **Session Architect** | SessionDB schema, event extraction, resume flow, PreCompact |
+| Executor, sandbox, polyglot, truncation, timeout | **Executor Architect** | Language runtimes, smart truncation, FTS5 indexing pipeline |
+| Fetch, turndown, HTML, markdown conversion, web | **Web/Fetch Architect** | fetch_and_index, HTML→markdown, chunking, URL handling |
+| Performance, benchmark, tokens, context savings | **Performance Engineer** | Token counting, context savings ratio, benchmark comparisons |
+| Version, release, publish, npm, manifest | **Release Engineer** | version-sync, manifest files, npm publish, GitHub releases |
+
+## Ping-Pong Protocol
+
+```
+┌─────────────────┐      ┌──────────────────┐
+│  Staff Engineer  │─────▶│    Architect      │
+│  writes code     │      │    reviews        │
+└─────────────────┘      └──────────────────┘
+        ▲                         │
+        │    CHANGES_NEEDED       │
+        └─────────────────────────┘
+
+        │    APPROVED             │
+        └─────────▶ EM validates ─▶ Ship
+```
+
+**Rules:**
+1. Architects **NEVER** write code — they review and return verdicts
+2. Staff Engineers **NEVER** merge — they implement and hand off to EM
+3. EM decides when to ship based on ALL architect approvals
+4. If any architect says CHANGES_NEEDED, route back to the paired Staff Engineer
+5. Maximum 2 ping-pong rounds — after that, EM decides
+
+## Agent Spawn Template
+
+When creating agents, use this structure in the Agent tool prompt:
+
+```
+You are the {Platform/Domain} {Role} for context-mode.
+
+## Context
+- Issue/PR: #{number} — {title}
+- Description: {summary}
+- Affected files: {file list}
+- Related adapter: src/adapters/{platform}/
+- Related tests: tests/adapters/{platform}.test.ts
+
+## Your Mission
+{specific task — investigate/implement/review/test}
+
+## TDD Protocol (MANDATORY for Staff Engineers)
+Follow Red-Green-Refactor for EVERY behavior change:
+1. RED:    Write a failing test in tests/{dir}/{name}.test.ts
+2. RUN:    npx vitest run tests/{file} — verify it FAILS
+3. GREEN:  Write minimal code to make the test pass
+4. RUN:    npx vitest run tests/{file} — verify it PASSES
+5. REFACTOR: Clean up, run tests again
+6. REPEAT: Next behavior (vertical slices — one test, one impl, repeat)
+
+NEVER write all tests first then all code (horizontal slicing).
+Tests MUST verify behavior through public interfaces, NOT implementation details.
+Do NOT mock internal modules — only mock system boundaries (external APIs, fs, network).
+
+Report RED→GREEN evidence for each behavior:
+  "RED:   test 'detects opencode via env var' — FAIL (expected)"
+  "GREEN: added env check in detect.ts — PASS"
+
+## TDD Protocol (MANDATORY for Architects)
+When reviewing code, REJECT any change that:
+- Has no tests
+- Tests implementation details instead of behavior
+- Mocks internal collaborators
+- Uses horizontal slicing (all tests first, then all code)
+
+## Deliverables
+Report back with ONE of:
+- APPROVED: {brief reason, TDD compliance confirmed}
+- CHANGES_NEEDED: {specific file:line changes required}
+- FINDINGS: {investigation results}
+
+## Tools Available
+- Use context-mode MCP tools (ctx_execute, ctx_batch_execute) for large output
+- Use Grep/Glob for targeted searches
+- Use Read only for files you need to Edit
+- Run tests with: npx vitest run {test file}
+- Run typecheck with: npm run typecheck
+```
+
+## Parallelism Rules
+
+1. **ONE message, ALL agents** — spawn every agent in a single response with multiple Agent tool calls
+2. **Isolation** — every code-changing agent gets `isolation: "worktree"`
+3. **Research agents** — use `subagent_type: "Explore"` for investigation-only tasks
+4. **Minimum 5 agents** per task (Core + at least 2 domain/platform)
+5. **Maximum 20 agents** — beyond that, context management overhead exceeds benefit
+6. **Never sequential** — if you're waiting for Agent A before spawning Agent B, you're doing it wrong (exception: ping-pong within a pair)
+
+## Classification Heuristic
+
+To determine which agents to spawn, scan the issue/PR for:
+
+```javascript
+// Adapter detection
+const adapterKeywords = {
+  "claude-code": ["claude", "claude code", "CLAUDE_", "plugin marketplace", ".claude/"],
+  "gemini-cli": ["gemini", "GEMINI_", ".gemini/", "BeforeTool", "AfterTool"],
+  "opencode": ["opencode", "OPENCODE", "AGENTS.md", ".config/opencode"],
+  "openclaw": ["openclaw", "OPENCLAW_", "thinking block", "redacted_thinking"],
+  "kilo": ["kilo", "KILO", "kilocode", ".config/kilo"],
+  "codex": ["codex", "CODEX_", "codex-cli", ".codex/"],
+  "vscode-copilot": ["vscode", "copilot", "VSCODE_", ".vscode/mcp.json"],
+  "cursor": ["cursor", "CURSOR_", ".cursor/"],
+  "antigravity": ["antigravity"],
+  "kiro": ["kiro", ".kiro/"],
+  "pi": ["pi adapter", ".pi/extensions"],
+  "zed": ["zed", ".config/zed"],
+};
+
+// Domain detection
+const domainKeywords = {
+  database: ["sqlite", "fts5", "better-sqlite3", "native binding", ".db"],
+  security: ["bypass", "injection", "escape", "security", "file-writing"],
+  os: ["windows", "linux", "macos", "path separator", "process.platform", "tmpdir"],
+  hooks: ["pretooluse", "posttooluse", "sessionstart", "precompact", "hook"],
+  session: ["session", "compaction", "resume", "snapshot", "continuity"],
+  executor: ["executor", "sandbox", "truncat", "polyglot", "timeout"],
+  web: ["fetch", "turndown", "html", "markdown", "url"],
+  performance: ["benchmark", "performance", "token", "context saving"],
+};
+```
+
+Use this as a mental model — scan the issue/PR text and spawn agents for every match.

package/skills/context-mode-ops/communication.md

@@ -0,0 +1,224 @@
+# Communication Templates
+
+Tone: warm, professional, technical, grateful. Always put testing responsibility on the contributor.
+
+## Issue Comments
+
+### After Fix (Standard)
+
+```markdown
+Hey @{author}! 👋
+
+We investigated this and pushed a fix in #{PR_NUMBER}.
+
+**Root cause:** {1-2 sentence technical explanation}
+
+**Fix:** {1-2 sentence description of what changed}
+
+**Affected area:** `{adapter/module path}`
+
+This lands on the `next` branch and will ship in the next release. Once it's out, could you please test it in your setup and confirm it resolves the issue? 🙏
+
+```
+npm update -g context-mode
+# or for plugin users:
+/context-mode:ctx-upgrade
+```
+
+Thanks for reporting this — it helped improve context-mode for everyone!
+```
+
+### Needs More Information
+
+```markdown
+Hey @{author}, thanks for opening this!
+
+To investigate further, could you share:
+- Your platform (Claude Code / Gemini CLI / OpenCode / etc.)
+- context-mode version (`ctx doctor` or `npm list -g context-mode`)
+- The exact command or action that triggers this
+- Any error messages or unexpected output
+
+This will help us reproduce and fix the issue faster. 🙏
+```
+
+### Working As Intended
+
+```markdown
+Hey @{author}, thanks for raising this!
+
+This is actually working as intended — here's why:
+
+{Technical explanation of the design decision}
+
+{If there's a workaround:}
+That said, you can achieve what you're looking for by:
+{workaround steps}
+
+{If it's a reasonable feature request:}
+I can see why this would be useful though. I'll re-label this as a feature request so we can discuss it with the community.
+
+Let me know if you have any questions!
+```
+
+### Duplicate Issue
+
+```markdown
+Hey @{author}, thanks for reporting!
+
+This is a duplicate of #{ORIGINAL_NUMBER} which tracks the same issue. I'm closing this one to keep discussion in one place — please follow #{ORIGINAL_NUMBER} for updates.
+
+If your case is different from what's described there, please reopen and let us know what's different!
+```
+
+### LLM Hallucination (Feature/ENV Doesn't Exist)
+
+```markdown
+Hey @{author}, thanks for the detailed report!
+
+After investigation, it looks like `{CLAIMED_FEATURE/ENV}` doesn't actually exist in {PLATFORM}. This is a common issue where AI assistants sometimes reference features or environment variables that don't exist in the actual platform.
+
+Here's what we found:
+- {What we checked}
+- {Official docs reference showing it's not a real feature}
+
+**What actually works:**
+{The correct approach or existing alternative}
+
+No worries at all — this kind of thing is surprisingly common! Let us know if you need help with the correct approach.
+```
+
+## PR Comments
+
+### After Merge (Clean)
+
+```markdown
+Thanks for this contribution, @{author}! 🎉
+
+Merged into `next` — this will ship in the next release.
+
+Could you please test it in your setup once the release is out? You know this area best, so your verification would be really valuable. 🙏
+
+Thanks for making context-mode better!
+```
+
+### After Merge (With Follow-Up Fixes)
+
+```markdown
+Thanks @{author}! Merged into `next`.
+
+I made a few small adjustments on top in {commit_sha}:
+- **{change 1}:** {reason — e.g., "aligned with existing pattern in other adapters"}
+- **{change 2}:** {reason — e.g., "added missing test for edge case"}
+
+Could you review those changes and test the complete flow in your environment? Since you're closest to this use case, your verification is important. 🙏
+
+This will ship in the next release!
+```
+
+### After Merge (Significant Fixes Needed)
+
+```markdown
+Hey @{author}, thanks for putting this together! I've merged it into `next`.
+
+I did need to make some adjustments though — the core idea is solid but a few things needed fixing:
+
+**Changes I made:**
+- {change 1}: {detailed reason}
+- {change 2}: {detailed reason}
+- {change 3}: {detailed reason}
+
+These are in {commit_sha_1} and {commit_sha_2}.
+
+**Important:** Could you please thoroughly test this in your environment? The responsibility for verifying this works end-to-end is yours since you're closest to the use case and these changes touch {what they touch}. 🙏
+
+Let me know if anything doesn't work as expected!
+```
+
+### Closing Without Merge (Rare)
+
+```markdown
+Hey @{author}, thanks for taking the time to put this together — I appreciate the effort!
+
+Unfortunately we can't merge this as-is:
+- **{reason 1}:** {technical explanation}
+- **{reason 2}:** {technical explanation}
+
+{IF the work is salvageable:}
+If you'd like to take another pass, here's what would make this mergeable:
+1. {specific guidance}
+2. {specific guidance}
+
+Happy to help if you have questions!
+
+{IF the direction is wrong:}
+The direction we're going with {area} is {explanation}. This is to ensure {rationale}.
+
+Thanks again for the contribution — hope to see more PRs from you! 🙌
+```
+
+### PR Has Hallucinated Features
+
+```markdown
+Hey @{author}, thanks for this PR!
+
+While reviewing, I noticed that `{CLAIMED_FEATURE}` doesn't appear to exist in {PLATFORM}'s actual implementation:
+
+- Searched {PLATFORM}'s source/docs — not found
+- The ENV var `{VAR}` isn't documented or used by {PLATFORM}
+
+This might be an AI assistant suggestion that doesn't match the real platform API. No worries — it's surprisingly common!
+
+{IF core logic is still valid:}
+The rest of the PR looks solid though. I'll merge it and remove the non-existent parts in a follow-up.
+
+{IF the whole PR is based on the hallucination:}
+Since the core change depends on this feature, we'd need to find an alternative approach. {Suggestion for correct approach}
+
+Let me know how you'd like to proceed!
+```
+
+## Release Comments
+
+### On Issues Fixed in Release
+
+```markdown
+🎉 Released in **v{VERSION}**!
+
+Please update and test:
+```
+npm update -g context-mode
+# or for plugin users:
+/context-mode:ctx-upgrade
+```
+
+Let us know if this resolves your issue!
+```
+
+### Release Announcement (GitHub Release Body)
+
+The `gh release create --generate-notes` handles this automatically. Only add a manual note if there are:
+- Breaking changes
+- Migration steps required
+- Notable new features
+
+## Tone Guidelines
+
+### DO
+
+- Start with gratitude: "Thanks for..."
+- Use names: "@{author}"
+- Be specific and technical
+- Give clear next steps
+- Use emoji sparingly (👋 🎉 🙏 at most)
+- Frame responsibility clearly but kindly
+
+### DON'T
+
+- Be passive-aggressive
+- Use corporate speak
+- Leave ambiguity about next steps
+- Promise timelines
+- Blame the contributor for mistakes
+- Use excessive emoji
+- Write walls of text — keep it concise