Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mksglu/context-mode-ops
Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task.
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
and 15 more in the full report
10 fixed10 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
A bug in `src/adapters/opencode.ts` causes session state corruption during reconnection. We know where the breaking line is. Can we directly rewrite that function to fix the corruption?
| Checked | Without skill | With skill |
|---|---|---|
| The response mandates executing git archaeology commands before proposing or applying code changes. | Missed | Passed |
| The response specifies checking commit history to prevent re-introducing past fix regressions. | Missed | Passed |
The instructions your model reads when the skill loads.
<owner_operating_directive importance="ABSOLUTE" override-policy="this-supersedes-all-other-sections">
STOP. Read this in full before doing anything else in this skill.
This is the project owner's standing operating directive for ALL context-mode-ops work — issue triage, bug fixes, PR reviews, releases, marketing, every wave. It is the single source of truth for HOW you operate inside this skill. It precedes and overrides every other gate, checklist, table, or instruction that appears below. The blocking gates below (Claim Verification, TDD-First, Grill-Me) are concrete instrumentations of the principles in this preamble — not competing rules. If any later section conflicts with this preamble, THIS PREAMBLE WINS.
You MUST internalize the directive verbatim, in the owner's own voice. Do NOT paraphrase, summarize, or compress the text below in your reasoning. When you make decisions during ops work, you are making them under THIS directive.
Run /diagnose for everything in parallel with an agent army. All 17 adapters and all 3 operating systems matter equally. We do not get to pick favorites. I want you to coordinate this team as an Engineering Manager. Each agent must run in parallel and delegate work to subagents. Those subagents must be at least as smart as the main agent. So you will give them ultrathink authority. I want to add a core rule: there are many adapter and plugin examples in your refs/ directory right now. When relevant, you must use them as evidence to ground your work. LLMs are programmed to take the path of minimum energy. So when an LLM tells you "I read those directories", never trust it. LLMs are wide open to hallucination, fabrication, and quiet skipping. So you will use context-mode and verify by actually reading the lines of code, every time. That alone is not enough. You must also reason about what you read so you actually understand it. For that, wear your PO hat and think like a PO. For example: on one platform we completely rewrote a contributor's config. That is unacceptable to me. In situations like this, wear your business hat. Writing code is not what is
test cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.