chalk

Plugin chalk from marketplace juxt-plugins in juxt/claude-plugins. Commands read from the repo's manifest — 3 days ago.

Skills (11)

• chalk

  chalk's root skill, and the entry point for a building session: plan in plan mode until the user approves the goal and the route, then keep the session's journal in the plan file. The skills that read or write the plan — commit, pr, put-down, sitrep — load this one for the plan file's shape and the

• code-comments

  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 editi

• commit

  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 t

• explicate

  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 when the

• goal-tree

  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 pr

• issue

  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

• pr

  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

• put-down

  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 s

• rubber-duck

  Rubber-duck a design with the user — take their thinking in whatever order it arrives, file each decision, constraint, question and idea under a stable ID as it goes, push back with consequences and conflicts, and keep a running record the user turns into whatever they want at the end. Use when the

• sitrep

  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 bre

• voice

  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-pros

Subagents (3)

• github

  Mechanics layer for the chalk skills — manages GitHub state (issues, comments, PRs, issue relationships). Handles `gh` calls for creating issues, updating issue descriptions, posting issue comments, creating PRs, reading and searching issue state, and managing sub-issue and blocked-by relationships.

• weed-comments

  Deletes code comments that don't earn their place, from the files a change touched. Applies `chalk:code-comments` — the default of silence, the exceptions, the test — against code it has never seen before, and lands the deletions. DO NOT invoke this agent directly from the main conversation, and DO

• weed-prose

  Reviews a drafted PR description or issue body as the artefact's pinned reader would — cutting sentences answerable from what that reader already holds, and reporting where the why is missing and where reasoning breaks the mindmap rules. Deletion-only; it never rewrites. DO NOT invoke this agent dir