All authors
Claude Skills by codecast-sh
github.com/codecast-sh33 skills0 installs79 views
- Cast From CallTurn a team call's action items into tasks people can pick up, each linked to the line in the transcript where it was agreed. Reads the call's summary and transcript, confirms each commitment against what was actually said, and files tasks marked as decided in a meeting. Use after a call, when asked what was agreed, or to file follow ups from a huddle; "chat" does the same for a chat thread.Votes: 0GitHub stars: 35
- Cast LessonsHarvest the corrections humans made across the team's sessions in a window, cluster them, and propose the guidance that would have prevented each. Reads every session where someone said stop, no, not like that, or redirected an agent, and turns the pattern into instruction lines, decisions, or a doc. Use for a weekly retro, when the same mistake keeps recurring, or when asked what the team keeps correcting.Votes: 0GitHub stars: 35
- Cast OrgTalk 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 as a small proposal that renders inline for them to approve. Use when asked who is working on what, to set up or review the org, to hire a lead or a head of people, or when the ch...Votes: 0GitHub stars: 35
- Cast PassHand this session to a teammate so it lands in their inbox with everything they need. Pins where the work stands and what is next, adds them as an owner, and sends them the brief. Use when work should continue under someone else, when a decision is theirs, or when asked to pass, hand over, or assign a session.Votes: 0GitHub stars: 35
- Cast ShipTake finished work through to merge. Commits in topical pieces, opens the pull request with a description that links the session, then binds this session to the pull request so review comments, failing checks and a stale branch wake it until the merge lands. Use when asked to ship, open a PR, or handle review feedback; "feedback" works the open threads on the current PR.Votes: 0GitHub stars: 35
- Cast TriageTidy the fleet of sessions so the inbox shows only what needs a person. Reads every session by who acts next, resolves the stalled ones, stashes the finished, kills the dead, and surfaces the few that need the human with a one line ask each. Use when the inbox is crowded, after a fan out, or when asked what all these sessions are doing.Votes: 0GitHub stars: 35
- Cast ModMake 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 or add something to codecast's interface, to build a dashboard or view over the fleet inside codecast, or when a fenced block type should render richly everywhere.Votes: 0GitHub stars: 35
- OrchestrateDrive a plan to completion by orchestrating implementer, reviewer, and critic agents across waves of parallel work. Use when the user says "orchestrate", "implement this plan", "execute plan", "drive this", or approves a plan for execution.Votes: 0GitHub stars: 34
- Added SkillFound through the declared skills path.Votes: 0GitHub stars: 34
- Default SkillFound by the default skills/ scan.Votes: 0GitHub stars: 34
- Domain SearchCheck domain name availability accurately across TLDs using registry RDAP APIs and registry whois. Use when the user asks to check, find, brainstorm, or verify domain names, or asks whether a domain is available, for sale, or expiring.Votes: 0GitHub stars: 34
- ImproveSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to i...Votes: 0GitHub stars: 34
- No FrontmatterJust prose.Votes: 0GitHub stars: 34
- Overlengthxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...Votes: 0GitHub stars: 34
- Unknown FieldCarries a field that is in neither the spec's six nor Claude Code's list.Votes: 0GitHub stars: 34
- Wrong NameA skill whose frontmatter name disagrees with its directory name.Votes: 0GitHub stars: 34
- Cast Ask TeamAsk the team a question without blocking on it. Posts the question to the team channel with the context needed to answer it cold, parks this session as dormant, and continues when an answer arrives. Use when a question is for a person who is not in this thread, when the human is away, or when asked to check with the team.Votes: 0GitHub stars: 34
- Cast BakeoffTry several approaches to the same problem in parallel and compare the results side by side. Forks this conversation once per approach, waits for the branches to settle, then lays out each branch's diff, evidence and cost with a verdict. Use when two or more designs are plausible and the cheapest way to choose is to build each, or when asked to bake off, race, or compare approaches.Votes: 0GitHub stars: 34
- Cast ConflictsBefore editing or fanning out work, find the live sessions on this repository that are changing the same files, show what they changed, and warn them. Use before starting a task that touches shared files, before spawning workers, or when asked who else is working on this.Votes: 0GitHub stars: 34
- Cast EodClose the working day so nothing is lost and tomorrow starts cold without cost. Checks every live session for an honest pinned state, writes handoffs for work that will pause, arms follow ups that should run overnight, tidies the inbox, and leaves a short digest. Use at the end of a working day or before a long pause.Votes: 0GitHub stars: 34
- Cast HandoffPackage the current work so the next session or a teammate can continue without reading this thread. Writes the decisions, the direction, what is verified, open questions and ordered next steps as a shared doc, pins the state, and optionally forks, spawns or hands the work to a session. Use before stopping, before a long pause, or when handing work over.Votes: 0GitHub stars: 34
- Cast LearnTurn what this session learned into guidance the next session and the team will read. Extracts corrections the human made, decisions taken, and gotchas found; writes project guidance into the repository's agent instructions, records decisions where they are searchable, and files the rest as a doc. Use at the end of a piece of work, after a correction, or when asked to remember something.Votes: 0GitHub stars: 34
- Cast LoopRun an autonomous loop that works through a queue of tasks one fresh session at a time, with verification as the gate and a human decision at merge. Sets up a recurring trigger that spawns a session per ready task, a precheck that spends nothing when the queue is empty, and the rules each run follows. Use for a backlog of small independent tasks, an overnight sweep, or when asked to loop, keep going until done, or run unattended.Votes: 0GitHub stars: 34
- Cast MorningStart the day with the state of everything that waits on the human or is ready to pick up: sessions that need input, pull requests with reviews or red checks, tasks ready to start, what teammates and overnight triggers did, unread team chat and mail. Use at the start of a working day, after time away, or when asked what needs attention.Votes: 0GitHub stars: 34
- Cast PickupRehydrate before working. Reads the bound task or plan, the pinned state, what the team did on this project recently, and the repository and tmux state, then names the work and the next three actions. Use at the start of a session, after a resume or compaction, or when asked to pick up work.Votes: 0GitHub stars: 34
- Cast PlanTurn a request into a plan the team can review before code exists. Explores the codebase, searches prior sessions and recorded decisions for earlier attempts, interviews the user on the open questions, then writes a codecast plan with tasks and dependencies ready for orchestrate. Use when work has several parts, when asked to plan, or before fanning work out to other sessions.Votes: 0GitHub stars: 34
- Cast RethinkStop and re-examine a piece of work from the top: what it was meant to be, what every earlier session did, which decisions constrain it, and whether the current direction still serves the intent. Reconstructs the history from the team's sessions, decisions and tasks before touching code. Use when a feature feels off track, after several failed attempts, or when asked to step back, rethink, or start over.Votes: 0GitHub stars: 34
- Cast ReviewReview another session's work from its transcript and diff, then deliver findings to that session or its owner. Reads what the session was asked to do, what it changed, and how it verified, and reports correctness, missed requirements and risks with file and line. Use when asked to review a session, a teammate's work in progress, or a worker spawned from this session.Votes: 0GitHub stars: 34
- Cast Second OpinionGet an independent review of the current change from a different model in a fresh context, then verify its findings and fold the real ones in. Use before shipping, after a long debugging session, or when asked for another model's view.Votes: 0GitHub stars: 34
- Cast StandupBuild a standup or digest for a time window from the team's agent sessions, commits, tasks, pull requests, calls and chat. Use for a daily standup, a weekly retro, or when asked what happened since yesterday.Votes: 0GitHub stars: 34
- Cast VerifyProve the work before calling it done, and leave the evidence where reviewers read it. Runs the repository's checks, exercises the change in the human's own browser or on the command line, captures screenshots or output, attaches them to the task and the thread, and only then marks the work done. Use before declaring done, before shipping, or when asked to verify.Votes: 0GitHub stars: 34
- Cast WhyExplain 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.Votes: 0GitHub stars: 34
- Cast WorktreeMove 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.Votes: 0GitHub stars: 34