Jartan-LLC/grimoire

Curated plugins for development workflows, for Claude Code and Codex.
## Setup
Claude Code:
text
/plugin marketplace add Jartan-LLC/grimoire
Then browse and install plugins:
text
/plugin
Codex:
bash
codex plugin marketplace add Jartan-LLC/grimoire
codex plugin add @grimoire
Under Codex:
It ignores plugin dependencies, so praxis needs gitwise installed
explicitly.
A Codex plugin cannot provide agents, so plugins that ship agents install
them into your Codex config on session start instead.
## Available Plugins
| Plugin | Description |
| claudivis | The key to Claude Code configuration -- how agents, skills, and commands work together |
| gitwise | GitHub conventions -- branch naming, commit format, issue/PR templates, and safe issue/PR referencing |
| praxis | Development workflow -- issue planning, implementation, PR creation, code review with specialized reviewers, and project conventions |
| pythonica | Comprehensive Python development -- patterns, testing, async, error handling, packaging, configuration, type safety, resilience, observability, Pydantic, and more |
| recursio | Build in parallel -- break up and delegate work to recursive subagents |
## Versioning & Releases
Each plugin follows semantic versioning and has its own
CHANGELOG.md. The root CHANGELOG.md lists the marketplace-v releases you
can pin.
To update:
In a Claude Code session, open /plugin, select grimoire on the Marketplaces
tab and choose Update marketplace. Turn on auto-update there to update at
each session start.
In a shell, run claude plugin update @grimoire.
In Codex, run codex plugin marketplace upgrade.
To pin a project to a marketplace release, set ref to a
marketplace-v tag in its .claude/settings.json:
json
"extraKnownMarketplaces": {
"grimoire": {
"source": { "source": "github", "repo": "Jartan-LLC/grimoire", "ref": "marketplace-v1.0.0" }
A pinned project gets newer plugin versions only when you move ref to a newer
marketplace-v tag.
In CI, anthropics/claude-code-action's pluginmarketplaces input takes no