develop

Develop and verify the Mycelium plugin across Claude Code and Codex hosts.

68|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/arjunrajlaboratory/mycelium --skill develop-arjunrajlaboratory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/arjunrajlaboratory/mycelium/tree/main/skills/develop
Command: npx skills add https://github.com/arjunrajlaboratory/mycelium --skill develop-arjunrajlaboratory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Changes to the Mycelium plugin can silently break one host while passing on the other, and stale plugin caches make test results unreliable. This Skill provides a disciplined workflow for developing, refactoring, and reviewing the Mycelium plugin itself so cross-host changes stay correct as a system. ## Core Features & Use Cases - Cross-host TDD workflow: Reproduce defects with red regression tests, generalize the defect pattern across the branch, and implement narrow fixes that keep shared behavior host-neutral. - Regression pattern library: A references file documents 30+ known defect classes (stale plugin caches, premature mutation, lock recovery races, lineage false positives) to audit before editing. - Real-host verification: Hash-verify installed artifacts, run lifecycle audits on both Claude Code and Codex, and follow an ordered release gate before tagging versions. - Use Case: When fixing a bug in Mycelium's Stop hook, use this Skill to write a failing regression test, sweep for the same pattern in sibling modules, run the full test ladder, and verify dispatch on both hosts before release. ## Quick Start Use the develop skill to fix a bug in the Mycelium plugin's lifecycle hooks and verify it on both Claude Code and Codex.

Frequently Asked Questions about develop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely modify the Mycelium plugin across Claude Code and Codex?

Follow the develop workflow: establish the release-candidate scope, reproduce the defect with a red regression test, generalize the defect pattern across the branch, implement a narrow host-neutral fix, then run the test ladder and real-host audits on both platforms.

Why does my Claude plugin change not appear during smoke testing?

The Claude plugin cache is keyed on the version string, so content changes under an unchanged version are served stale. Remove the cached version directory and reinstall, then hash-compare source and installed files before auditing.

What regression patterns should I check before editing Mycelium hooks?

Read references/regression-patterns.md, which documents over 30 defect classes including validation after mutation, retry state cleaned before acceptance, lock recovery races, and fabricated data lineage. Audit each pattern relevant to the touched modules.

Does this skill cover responding to Codex PR review comments?

No. Responding to an existing Codex PR comment is handled by the separate codex-review skill. This skill covers developing, refactoring, and reviewing the Mycelium plugin source itself.

What is the correct release order for a Mycelium plugin version?

Merge to the default branch first, refresh and hash-verify the installed artifact, run lifecycle audits on both hosts, execute the release gate from a clean disposable clone, and tag the exact certified commit last.