daily-driver

This skill should be used whenever the Conventional Commits type of a change is being chosen or checked — including when the user asks "is this a fix or a feat?", "what type should this PR be?", "should this be a refactor?", says "the type is wrong" or "that's not a fix", questions what version merging will cut, or when a Projected Releases comment on a pull request disagrees with what the author meant; and whenever `pr-title` needs the type for a title it is writing. Supplies the two gates and the one test that pick the type from what the change does, and what the type decides about the next release. Not for writing the title itself — that is `pr-title` — and not for commit messages, which are not Conventional Commits in this toolkit.

This skill should be used whenever a relationship between GitHub issues is being recorded, read, or relied upon — one issue blocking another, a sub-issue or parent, or which pull request closes an issue. It fires on the literal "/issue-deps", on natural phrasings ("this is blocked by #123", "what's blocking this", "make it a sub-issue of the epic", "what does this depend on"), on noticing while planning or while writing a PR body that some other work must land first, and on Claude's own use of `mcp__github__sub_issue_write`, `mcp__github__issue_read` with `get_sub_issues` or `get_parent`, `mcp__github__issue_write` with `parent_issue_number`, or of a `Closes #123` line in a pull request body. Supplies the two clients these relationships need, the script for the half the MCP cannot reach, and the rule that a relationship is proposed from evidence and confirmed by the user, never asserted.

This skill should be used at the moment a choice between ways of doing the same task is about to be put to the user — on Claude's own use of `AskUserQuestion`, on a reply about to offer alternatives where one is quicker, less complete, or a departure from the standard way ("fix it properly, or leave a TODO?", "which approach do you prefer?", "should I …, or …?"), and when the user hands the same choice back ("properly, or a TODO?", "you decide"). It also fires on "/judgement-call", "just decide", "you pick", "use your judgement" (or "judgment") and "stop asking me". Supplies the test that separates a question only the user can answer from one Claude can answer himself, and the rule that answers the second kind. It waives no confirmation another rule requires — `issue-deps`'s edge confirmation, `review`'s walkthrough offer — and relaxes nothing governing an irreversible, destructive or outward-facing action.

This skill should be used whenever a GitHub pull request is being opened for the current branch, or an existing one is being brought up to date as a whole — including when the user says "/pr", "open a PR", "create a PR", "raise a pull request", or "update the PR", and including any call Claude makes on its own initiative to `mcp__github__create_pull_request`, to `mcp__github__update_pull_request` for anything wider than the title or the body alone, or to `gh pr create` / `gh pr edit` on a harness that still reaches for them. Supplies the branch guard, the existing-PR check, draft state and the call on whether there is an issue to reference; the title comes from `pr-title` and the body, issue reference included, from `pr-body`.

This skill should be used whenever the body of a GitHub pull request is being written or revised — including when the user says "rewrite the PR description", "update the PR body", "the PR description is thin", or asks for more detail in a PR, and including any call Claude makes on its own initiative to `mcp__github__create_pull_request`, to `mcp__github__update_pull_request` that sets a `body`, or to `gh pr edit --body` on a harness that still reaches for it. Supplies the required structure: one-line summary, salutation in verse, executive summary, engineering detail, and the issue-reference section that closes it. Not for the PR title — that is `pr-title`.

This skill should be used whenever the title of a GitHub pull request is being written or revised — including when the user says "fix the PR title", "rename the PR", "that title is wrong", or asks what a PR should be called, and including any call Claude makes on its own initiative to `mcp__github__create_pull_request`, to `mcp__github__update_pull_request` that sets a `title`, or to `gh pr edit --title` on a harness that still reaches for it. Supplies the Conventional Commits convention the title must conform to; the type itself comes from `conventional-commits-type`. Not for commit messages, not for the PR body — that is `pr-body` — and not for the session's own name — that is `session-title`.

This skill should be used whenever a pull request is being reviewed and that review is then answered — including when the user says "/review-cycle", "review the PR and fix what it finds", "address the review feedback", "reply to the review comments", "resolve those threads", or "does that need another review?", and including any call Claude makes on its own initiative to the built-in `/code-review` aimed at a pull request, to `mcp__github__add_reply_to_pull_request_comment`, or to `mcp__github__resolve_review_thread`. Supplies the wait for CI on the pushed head — the mechanism, not only the rule — the review invocation and its named effort level, the protocol every finding is answered under, and the test for whether a later push has earned a second round. Do NOT use this skill for opening a pull request or bringing one up to date — that is `pr` — nor for marking a draft ready, which is the caller's gate and not part of the round.

This skill should be used whenever the title of the current Claude session is being set or revised — including when the user says "/session-title", "set the session title", "rename this session", "name this session", or "that session title is wrong", and on Claude's own initiative when work on a GitHub issue begins, when the session's subject changes materially, or on any call to `mcp__Claude_Code_Remote__set_session_title`. Supplies the character budget a title is written to for the Claude mobile list, and the two forms that title may take. Not the title of a pull request — that is `pr-title`.