skills.rest
missingbulb
missingbulbCOMMUNITY
Explore all skills by this author →
GitHub

writing-handover-issues

Writes GitHub issue checklists that a human executes step by step.

Updated Jun 12, 2026
Search Tags:#documentation#checklist#onboarding#github issues#handover#task writing#human tasks
One-click install
npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill writing-handover-issues-missingbulb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-handover-issues
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/basics/skills/writing-handover-issues
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill writing-handover-issues-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issues written for a person to execute are usually written like descriptions, so the reader skims, loses the thread, and completes only some of the steps. This Skill restructures such issues so every required click, setting, or copy action actually gets done. ## Core Features & Use Cases - Two-part body structure: Puts a pure checkbox checklist first and moves all background, rationale, and links below it under their own heading. - Actionable step rules: Enforces one imperative action per line, deep links to the exact settings screen, and explicit instructions for where a generated value appears on the page. - Ordering and verification guidance: Pairs value-producing steps with value-consuming steps, drops no-op checkboxes, and ends with one observable confirmation of completion. - Use Case: When filing a GitHub issue asking a maintainer to register an OAuth app, set repository variables, and verify sign-in, use this Skill to produce a checklist they can execute top to bottom without prior context. ## Quick Start Write a handover issue for a human to configure the repository secrets and verify the deployment, with one checkbox per action and deep links to each settings screen.

Frequently Asked Questions about writing-handover-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a GitHub issue that a person will execute step by step?▼

Put a pure checkbox checklist first with one imperative action per line, then move all background and rationale below it under a separate heading. Each step should link directly to the exact settings screen rather than describing a navigation path.

How should I write steps that involve copying secrets or generated values?▼

Name the control that mints the value, where it appears on screen, and what it looks like, and say so in the step if it is shown only once. Place the step that produces the value immediately before the step that pastes it, using identical names in both.

When should a task get its own handover issue instead of a PR note?▼

Any work only a human can perform, such as registering an app, setting repository variables, or verifying production behavior, belongs in its own issue. A note in a PR body gets skimmed and skipped, while a dedicated checklist issue is built to be executed.

What are common mistakes when writing handover checklists?▼

Common defects include steps that explain instead of instruct, breadcrumb trails instead of deep links, steps ordered so a value is needed before it is minted, and no-op checkboxes that teach readers to skim. The fix is one action per line, verified links, and producer-consumer pairing.

Does this apply to issues describing work I will do myself?▼

No. Issues you will act on are descriptions and follow normal writing conventions. This Skill applies only to issues whose body asks another person to click, set, register, install, or copy something.

Related Skills

Explore More Product & Management Skills→
tonone-aitonone-ai
69

relay-audit

Audit CI/CD pipelines for slowness, security issues, and reliability gaps.

Official
Advanced
chris-prenerchris-prener

backlog-retrospective

Closes GitHub issues with structured retrospective comments and validates shipped outcomes.

Community
Advanced
bordenetbordenet
8

link-verification

Validate and verify Markdown links in documentation before publishing.

Community
Advanced
afterworkafterwork

aif-security-checklist

Apply OWASP-based security audit checks to code, configuration, and dependencies.

Official
Advanced