context-mode 1.0.111 → 1.0.113

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

@@ -1,224 +0,0 @@
-# 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

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

@@ -1,124 +0,0 @@
-# Marketing workflow
-
-## Trigger
-
-User says: "linkedin post", "marketing", "announce release", "write post", "share update"
-
-## Voice: Solo technical founder
-
-You are Mert. You built context-mode alone. You write like an engineer who happens to run a product, not like a marketing team. Your audience is technical VCs, senior engineers, and open source maintainers.
-
-<writing_rules>
-MANDATORY. Every word you write must pass these rules.
-
-1. NO em dashes. Not one. Use commas, periods, or rewrite the sentence.
-2. NO promotional language: "groundbreaking", "revolutionary", "game-changing", "seamless", "cutting-edge"
-3. NO significance inflation: "pivotal", "testament", "vital role", "evolving landscape"
-4. NO negative parallelisms: "not just X, it's Y" or "not X but Y"
-5. NO rule of three: stop forcing ideas into groups of three
-6. NO vague attributions: "experts say", "industry observers"
-7. NO filler: "in order to", "it is important to note", "at its core"
-8. NO generic conclusions: "the future looks bright", "exciting times ahead"
-9. NO sycophantic tone: "great question!", "I hope this helps!"
-10. NO copula avoidance: use "is/are/has" instead of "serves as/stands as/represents"
-11. NO excessive hedging: "could potentially possibly"
-12. NO AI vocabulary: "delve", "tapestry", "interplay", "foster", "landscape" (abstract)
-13. NO boldface headers in lists
-14. NO emojis
-
-DO:
-- Start with a personal confession or specific frustration
-- Use "I" freely. You are one person, not a company.
-- Vary sentence length aggressively. Short. Then longer ones that breathe.
-- Be specific: exact numbers, real platform names, actual pain points
-- Acknowledge uncertainty and mixed feelings when they exist
-- Let some mess in. Rougher transitions are more human.
-- Close with a genuine belief, not a sales pitch
-</writing_rules>
-
-## Data verification: MANDATORY
-
-<data_enforcement>
-Every number in the post MUST come from a real source. Do NOT invent metrics.
-Before writing, read these files and use ONLY verified numbers:
-</data_enforcement>
-
-| Data point | Source |
-|-----------|--------|
-| Total users | `stats.json` field `message` |
-| npm installs | `stats.json` field `npm` |
-| Marketplace installs | `stats.json` field `marketplace` |
-| Current version | `package.json` field `version` |
-| Platform count | `src/adapters/detect.ts` (count platforms in validPlatforms array) |
-| Adapter count | `tests/adapters/` (count test files) |
-| GitHub stars | `gh api repos/mksglu/context-mode --jq '.stargazers_count'` |
-| GitHub forks | `gh api repos/mksglu/context-mode --jq '.forks_count'` |
-| Open issues | `gh issue list --state open --json number --jq 'length'` |
-| Recent release | `gh release list --limit 1` |
-
-If you cannot verify a number, do not use it.
-
-## Workflow
-
-### 1. Gather real data (via agent)
-
-Spawn a Data Engineer agent to collect all numbers from the sources above. Wait for verified data before writing anything.
-
-### 2. Identify what changed
-
-Read the latest commits, release notes, or user request to understand what is being announced.
-
-### 3. Write draft
-
-Follow the writing rules above. Structure:
-
-```
-Hook (personal, specific pain or confession)
-Context (what is context-mode, real numbers)
-Problem (specific frustration, not abstract)
-Solution (what you built, how it works technically)
-Technical details (casual, woven in, not a spec sheet)
-Belief (where this is going, honest, not hype)
-Links (repo + install command)
-```
-
-### 4. Anti-AI audit
-
-After writing, ask yourself:
-- Would a real founder post this or would they cringe?
-- Is every number verified?
-- Are there any em dashes? (search for the character)
-- Any "pivotal", "testament", "landscape", "foster", "delve"?
-- Any lists of exactly three items forced together?
-- Does it sound like it was assembled or like someone actually wrote it?
-
-Fix every issue found.
-
-### 5. Output
-
-Write the final post to a file: `linkedin-post-v{VERSION}.md`
-
-Include three sections in the file:
-1. Final post text (ready to paste into LinkedIn)
-2. Data sources used (which files/commands provided which numbers)
-3. AI pattern audit results (what was caught and fixed)
-
-## Examples of good vs bad
-
-Bad (AI-generated):
-"We're thrilled to announce context-mode v1.0.57, a groundbreaking update that represents a pivotal moment in the evolution of AI-powered development tools. This release showcases our commitment to innovation, performance, and developer experience."
-
-Good (founder voice):
-"I have a confession. I built a tool used by 57,000+ developers and I was drowning in GitHub issues."
-
-Bad:
-"The technical architecture features a robust FTS5 search engine, a polyglot execution sandbox, and a dynamic agent orchestration layer, ensuring seamless integration across platforms."
-
-Good:
-"Some numbers on the tech side: FTS5 search with BM25 ranking, sandbox execution in 11 languages, session state survives context window compactions through SQLite event tracking."
-
-Bad:
-"This innovative solution serves as a testament to the transformative potential of AI-native infrastructure."
-
-Good:
-"Solo maintainers will run engineering orgs made of agents. Not because it sounds cool on a slide, but because the alternative is burnout."

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

@@ -1,214 +0,0 @@
-# Release Workflow
-
-## Trigger
-
-User says: "release", "version bump", "npm publish", "ship it"
-
-## Pre-Flight Checks
-
-Before ANY release action, verify:
-
-```bash
-# Must be on main branch
-git branch --show-current  # expect: main
-
-# Must be clean
-git status --porcelain  # expect: empty
-
-# Must be up to date
-git pull origin main
-```
-
-## Step-by-Step
-
-### 1. Validate Codebase (Parallel Agents)
-
-Spawn these agents simultaneously:
-
-| Agent | Task |
-|-------|------|
-| **QA Engineer** | Run `npm test` + `npm run typecheck` — report full pass/fail |
-| **Security Engineer** | Check for any open security issues, audit recent changes |
-| **Release Engineer** | Check current version, changelog, unreleased commits |
-| **DX Engineer** | Verify README is current, install instructions work |
-
-All must report PASS before proceeding.
-
-### 1b. Grill-Me Review — MANDATORY BLOCKING GATE
-
-**Before ANY version bump, the EM MUST run a grill-me interview on all changes in this release.**
-
-This is not optional. This is not skippable. Every release gets grilled.
-
-Interview the user relentlessly about every aspect of the changes until reaching shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ask questions one at a time. If a question can be answered by exploring the codebase, explore the codebase instead of asking.
-
-**The release is BLOCKED until:**
-- [ ] All branches of the design tree are resolved
-- [ ] Zero unresolved questions remain
-- [ ] User explicitly approves the grill results
-
-Only after grill-me approval: proceed to version bump.
-
-### 2. Version Bump — MANDATORY
-
-<version_bump_enforcement>
-You MUST run `npm version patch`. This is NOT optional. Do NOT skip this step.
-Do NOT manually edit package.json version. Do NOT create git tags manually.
-`npm version patch` does EVERYTHING — bump, sync manifests, stage, commit, tag.
-</version_bump_enforcement>
-
-```bash
-npm version patch
-```
-
-This single command does ALL of the following automatically:
-1. Bumps `package.json` version (e.g., 1.0.56 → 1.0.57)
-2. Triggers `version` lifecycle hook → runs `scripts/version-sync.mjs`
-3. `version-sync.mjs` syncs version to ALL 6 manifest files:
-   - `.claude-plugin/plugin.json`
-   - `.claude-plugin/marketplace.json`
-   - `.openclaw-plugin/openclaw.plugin.json`
-   - `.openclaw-plugin/package.json`
-   - `openclaw.plugin.json`
-   - `.pi/extensions/context-mode/package.json`
-4. Stages the manifest files via `git add`
-5. Creates a git commit and `v{VERSION}` tag
-
-**Do NOT create your own commit or tag. `npm version patch` handles it.**
-
-### 3. Validate (NO Build Needed)
-
-**Do NOT run `npm run build` or `npm run bundle`.** CI generates bundle files automatically on GitHub. You only validate:
-
-```bash
-# Tests
-npm test
-
-# TypeScript
-npm run typecheck
-```
-
-### 4. Git Tag & GitHub Release
-
-```bash
-# The npm version command already created a git tag
-# Verify it exists:
-git tag --list 'v*' | tail -5
-
-# Push the commit and tag
-git push origin main --tags
-
-# Create GitHub release with auto-generated changelog
-gh release create v{VERSION} \
-  --title "v{VERSION}" \
-  --generate-notes \
-  --latest
-```
-
-### 5. npm Publish (Local)
-
-**⚠️ REQUIRES USER APPROVAL — ask before running.**
-
-```bash
-# Dry run first
-npm publish --dry-run
-
-# If dry run looks good, publish
-npm publish
-```
-
-Verify publication:
-```bash
-npm view context-mode version  # should show new version
-```
-
-### 6. Sync Branches
-
-Sync `next` with `main` to ensure next has all release changes:
-
-```bash
-# Fetch latest
-git fetch origin
-
-# Merge main into next
-git checkout next
-git pull origin next
-git merge main --no-edit
-
-# Push
-git push origin next
-
-# Return to main
-git checkout main
-```
-
-**If merge conflict:** Resolve in favor of `main` (release branch is authoritative).
-
-### 7. Clean Remote Branches
-
-**⚠️ REQUIRES USER APPROVAL for EACH branch.**
-
-List stale remote branches (everything except `main` and `next`):
-
-```bash
-# List remote branches excluding main and next
-git branch -r | grep -v 'origin/main' | grep -v 'origin/next' | grep -v 'origin/HEAD'
-```
-
-For each branch, ask the user:
-```
-Remote branch: origin/{branch-name}
-Last commit: {date} — {message}
-Related PR: #{number} ({state})
-
-Delete this branch? [y/n]
-```
-
-Only delete after explicit approval:
-```bash
-git push origin --delete {branch-name}
-```
-
-## Release Checklist (EM Verification)
-
-Before declaring release complete:
-
-- [ ] `npm test` — all pass
-- [ ] `npm run typecheck` — no errors
-- [ ] `npm version patch` — version bumped in all manifests
-- [ ] `git push origin main --tags` — pushed with tag (CI builds bundles automatically)
-- [ ] `gh release create` — GitHub release published
-- [ ] `npm publish` — package on npm registry
-- [ ] `next` branch synced with `main`
-- [ ] Stale remote branches cleaned (user approved)
-- [ ] Verify: `npm view context-mode version` shows new version
-
-## Rollback Plan
-
-If something goes wrong after publish:
-
-```bash
-# Unpublish within 72 hours (npm policy)
-npm unpublish context-mode@{BAD_VERSION}
-
-# Or deprecate
-npm deprecate context-mode@{BAD_VERSION} "Known issue: {description}"
-
-# Revert git
-git revert HEAD
-git push origin main
-```
-
-## Post-Release
-
-After successful release:
-
-1. Comment on all issues fixed in this release:
-   ```
-   Released in v{VERSION}! Please update and test:
-   npm update -g context-mode
-   ```
-
-2. Update Discord if there are noteworthy changes
-
-3. Check npm download stats in 24h for any anomalies