Skill Claude Code
Explain why a line of code is the way it is. Traces the line through cast blame to the codecast session that wrote it and the message where it was decided, then answers from the author's own reasoning. Use when asked why code looks like this, who wrote it and why, or what the intent behind a change was.
Skill Claude Code
Move this work into an isolated worktree with its own env files, ports and setup, so it cannot collide with other sessions in the shared checkout. Use before parallel work, before a risky change, when another session is editing the same files, or when asked to work in a worktree.
Skill Claude Code
Talk through the organization of agents and people around this work with the person, in this session: who reports to whom, what each role looks after, where their sessions go. Reads what the code and the sessions say before it trusts a plan or a task, asks what the records cannot settle, and posts each agreed change…
Skill Claude Code
Make a codecast mod, a small sandboxed module that adds panes, commands and new kinds of blocks agents can draw to the codecast app, and that reads the person's sessions, tasks, plans, PRs and more. Use when asked to customize, extend, retheme or add something to codecast's interface, to build a dashboard or view over…
Skill Claude Code
Build a live dashboard as a published page over the team's work record (tasks, sessions, spend, pull requests, signals) and its product data (metrics, events, PostHog, connectors). Every chart shows its query and when it last refreshed, and refreshes itself. Use when asked for a dashboard, a live report, a metrics…
Skill Claude Code
Make an animated explainer from code and a timeline, published as a codecast page that plays, scrubs, takes comments pinned to moments, can show live numbers, and exports to MP4 on request. Use when asked for a motion piece, an animated explainer, a video of a dashboard or of what the team shipped, or to turn data…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: