chalk
v0.36.0Capture intent across issues, commits, and PRs — why, not just what
By JUXTLicense: MIT10 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 10 skill or MCP entries
- Source updated
- Oct 13, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install chalk for Codex and Claude Code
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add chalk@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/juxt/claude-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/chalk/.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/code-comments/SKILL.md├── skills/commit/SKILL.md├── skills/explicate/SKILL.md├── skills/goal-tree/SKILL.md├── skills/issue/SKILL.md├── skills/pick-up/SKILL.md├── skills/pr/SKILL.md├── skills/put-down/SKILL.md├── skills/sitrep/SKILL.md└── skills/voice/SKILL.md
Included Skills10
What earns a code comment, and what to delete — the default of silence, the moves that dissolve a comment before you write it, the exceptions that earn one, the pinned readers and the test, and where rejected material goes instead. Load early in any session that touches code, before writing or editing any comment, docstring or kdoc, and again when reviewing a diff, where weeding the comments is part of the review.
Create a commit with a contextual body explaining the why, in the chalk voice. Use when the user says "commit this", "commit", "make a commit", "/chalk:commit"; OR is about to compose, draft, write or amend any git commit message body (e.g. "write a commit message", "draft the commit body", "amend the commit message"). Load this skill BEFORE drafting any such prose — it carries the voice guidance the commit body needs.
Explicate an area of the codebase for an engineer catching up on it — how it works now, the decisions that shaped it and their consequences elsewhere, grounded in the code and its recorded history — then answer follow-ups as a depth-first walk, keeping track of where the user has been. Use only when the user runs "/chalk:explicate".
Structure a goal as a tree whose children accomplish their parent rather than argue for it, and test each node for sufficiency. Load whenever writing something with a goal structure in it — the direction or target end state of a piece of work, an issue's Potential approach section, the shape of a problem, or a plan. Covers the sufficiency test, the three kinds of leaf, and the named moves for closing a gap. The chalk:issue skill loads it alongside chalk:voice.
Create a GitHub issue, or update an existing issue's description, with a body that captures the problem and why it matters, in the chalk voice. Use when the user says "open an issue", "file a bug", "raise an issue", "create an issue", "file a ticket", "write up a feature request", "/chalk:issue"; OR is about to compose, draft, write or update any GitHub issue title, issue body or issue description (e.g. "write up an issue for this", "update the issue description", "put the analysis on the ticket"). Load this skill BEFORE drafting any such prose — it carries the voice guidance the body needs.
Pick up an issue's work in this session — read the issue and its neighbourhood, report what the scan found, sort the tracker metadata, and start the plan that journals the session's decisions, questions and constraints as they happen, so its commits and PR are written from them. Use when the user says "pick this up", "pick up
Create a pull request with a description that captures the intent and reasoning behind the change, in the chalk voice. Use when the user says "create a PR", "open a PR", "submit a PR", "raise a PR", "make a PR", "PR this", "/chalk:pr"; OR is about to compose, draft, write or update any pull request title or body (e.g. "write a PR description", "draft the PR body", "update the PR description", "let's put that in the PR"). Load this skill BEFORE drafting any such prose — it carries the voice guidance the PR body needs.
Park the session's work on its issue, so the next session can resume from the issue and its links alone — the description corrected, the metadata sorted, and cards the session discovered raised and linked as appropriate. Use when the user says "put this down", "park this", "/chalk:put-down", or is switching this session away from the issue's work.
Report where the current session has got to as a mindmap — what has landed, what is still open as ID'd ideas, decisions and questions, and a tl;dr. Use when the user says "/sitrep", "where are we", "where were we", "recap the session", "what's still open", or is picking a session back up after a break, a compaction or a handover.
Shared Chalk writing voice — the audience for Chalk artefacts, the specification register, the mindmap structure that two propositions in a relation MUST take, and the layout rules. The chalk:issue, chalk:commit, chalk:pr and chalk:sitrep skills load this before drafting any prose, and the weed-prose agent loads it to review one.
Plugin manifests2
{
"name": "chalk",
"version": "0.36.0",
"description": "Capture intent across issues, commits, and PRs — why, not just what",
"author": {
"name": "JUXT",
"url": "https://juxt.pro"
},
"homepage": "https://github.com/juxt/claude-plugins/tree/master/plugins/chalk",
"repository": "https://github.com/juxt/claude-plugins",
"license": "MIT",
"keywords": [
"github",
"issues",
"commits",
"pull-requests",
"agent-memory"
],
"skills": "./skills/",
"interface": {
"displayName": "Chalk",
"shortDescription": "Keep coding intent with the work",
"longDescription": "Preserve the reasoning behind your work in issue descriptions, commits, and pull requests — written for whoever picks it up next.",
"developerName": "JUXT",
"category": "Coding",
"capabilities": [
"Read",
"Write",
"Interactive"
],
"websiteURL": "https://github.com/juxt/claude-plugins/tree/master/plugins/chalk",
"defaultPrompt": [
"File an issue capturing the problem and why it matters now.",
"Create a commit that captures why this changed.",
"Open a pull request explaining this change."
],
"screenshots": []
}
}{
"name": "chalk",
"version": "0.36.0",
"description": "Capture intent across issues, commits, and PRs — why, not just what"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[chalk on Agent Plugins Marketplace](https://pluginsmp.com/plugins/chalk)