hy0sh-skills

Plugin hy0sh-skills from marketplace claude-skills in Hy0sh/claude-skills. Commands read from the repo's manifest — 2 days ago.

Skills (15)

• dailysum

  Generate the user's own portion of a collaborative daily sum (the work done today), to paste into the team's Slack Canvas. Use when the user asks for their daily, dailysum, a summary of today's work or a daily project recap, in any language ("mon daily", "résumé des travaux du jour").

• demo-pr

  Use when a pull request or a branch has to be shown working to a human before it is marked ready or merged — a reviewer, a PO or the author wants to see the change run, or an orchestrator collects one demo per worker. The agent first decides whether a video is worth it (a user journey across several

• demo-rec

  Use when a web app, or a command line tool through a terminal, has to be filmed doing something — a demo video of a feature, a pull request, a bug reproduction — with `demo-rec`, a Go CLI that plays a declarative YAML scenario headless, checks that each expected text is on screen, and writes an mp4

• jira-read

  Use when a task needs to read Jira — find which ticket the current branch, commits or PR are about, read a ticket in full with its comments, sub-tasks and links, or search tickets with JQL. The canonical read route (acli first with explicit fields, ADF flattened, Atlassian MCP as fallback) that othe

• notify-pr-slack

  Use when the user asks to announce a pull request on Slack to get it reviewed — "ask for a review", "post the PR on Slack", "announce my PR", "review please", or the same in another language ("demande de review", "poste la PR sur Slack") — for the current branch or for a pull request given by number

• overlapping-prs

  Plan how a set of pull requests that overlap — same files, same schema migration chain, same shared code — are cut, ordered and merged so that they stop colliding with each other: shared foundation first, a merge order fixed up front with a stack that follows it, and schema migrations kept as the la

• pr-watch

  Take stock of the user's own open pull requests in one pass — conflicts with the base branch, CI verdict, unanswered review threads, and position in a stack — then propose an ordered list of actions. Use when the user asks for the state of their PRs, asks which ones are blocked, mentions conflicts a

• review-diff

  Use when a diff has to be reviewed for correctness before it ships — the current branch or working tree against its base, with no pull request needed. The canonical review method (dimensions, self-refutation, severity gate, runtime confirmation of every blocker and major) that review-pr and ticket-t

• review-pr

  Use when a GitHub pull request, given by number, has to be reviewed — a first pass, or a re-review after the author pushed fixes. Checks the PR out in its own worktree, follows review-diff, reads the CI instead of rerunning it, and drafts the inline comments in the reviewer's voice for them to post.

• review-retro

  Use when the user wants fewer review comments on their own pull requests, asks why reviewers keep finding things their self-review missed, or asks to improve the review skills (review-diff, ticket-to-pr) or a repository's review checklist from the feedback they actually received, or asks to replay t

• sprint-check

  Cross-check the user's assigned Jira tickets against the real state of the code — merged, open and draft pull requests — to surface the statuses that are wrong, the tickets nobody has taken, and which ticket is the next logical one to pick up, with the reason. Use when the user asks for a tour of th

• ticket-to-pr

  Use when taking a Jira ticket from the ticket to the pull request — the user asks to work, take, handle, start or develop a ticket by its key, or asks whether a ticket is feasible and already covered before coding it. Covers prior art, the feasibility verdict, the isolated worktree and its stack, an

• visual-plan

  Use when a plan, an analysis or a verdict written in markdown is about to be handed to a human for approval or reading — a plan parked for the user, a spec to validate, a design to arbitrate — and the user would rather review a page than read the markdown, or asks for a "more visual" plan.

• wtm-setup

  Use when a project has to be registered in the `wtm` (worktree-manager) registry, or a registered project's settings changed — the base branch, the pre-migrated dump, the migration command, the database wiring, the seed of a fresh worktree. Discovers the compose file, asks only what discovery cannot

• wtm

  Use when working, running, testing or visually verifying anything inside a git worktree backed by worktree-manager (`wtm`), or when a new isolated worktree is needed for a task. `wtm` is a Go CLI that creates a worktree with its own Docker Compose stack (remapped ports, separate volumes) and a pre-m

Hooks (4)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/wtm-guard"

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/wtm-context"

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/skills-index"

• SessionEnd

  "${CLAUDE_PLUGIN_ROOT}/hooks/wtm-sweep"