Claude Code 自定义技能：夜间自动开发与晨间汇报工作流

Highly recommend 𝘀𝗮𝘃𝗶𝗻𝗴 𝘁𝘄𝗼 𝗰𝗼𝗺𝗺𝗮𝗻𝗱𝘀 in Claude Code: /night before bed, /morning when you wake up.

Say there's a dark mode you've been meaning to add but never had time for. Before bed, type "/night add dark mode" and Opus 5.5 builds it on a new branch, runs the tests and leaves you a note. In the morning, type /morning: it tells you which pages it changed overnight, then asks you 𝘁𝗵𝗲 𝘁𝘄𝗼 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗼𝗻𝗹𝘆 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗮𝗻𝘀𝘄𝗲𝗿: follow the system setting, or add a toggle? Should the charts go dark too? Each one has its recommended answer marked. Reply "1A 2A" and it finishes the rest.

Before bed, check: → Keep the computer awake. In the Claude desktop app, turn on Keep computer awake while Claude works under Settings → Claude Code. In the terminal on a Mac, start it with caffeinate -i claude instead. Plug it in and keep the lid open; a closed lid still sleeps. → Make sure you're in auto mode: the terminal status bar shows auto mode on, the default since 2.1.283. If not, press Shift+Tab to switch. Otherwise it stops to ask for your OK before most file edits and commands. → The disallowed-tools: AskUserQuestion line in night turns off the question pop-up. It won't stop in the middle of the night to ask you something; anything it's unsure about goes in the note for the morning.

Create night and morning folders in ~/.claude/skills/ with a SKILL.md in each, and they work in every project on this computer. Don't want to make folders? Paste both into Claude Code and have it save them for you 👇

night/SKILL.md --- description: Give Opus 5.5 one job it can finish on its own before bed argument-hint: "[what to build tonight]" disable-model-invocation: true disallowed-tools: AskUserQuestion --- I'm going to sleep. Tonight, work on this: $ARGUMENTS If I didn't say, pick one thing in this project you can finish tonight and test yourself. Before you start, write one line in NIGHT_NOTE.md saying what you're doing. - Create a new branch and only change things there. Commit to that branch when you're done; don't push. Don't commit NIGHT_NOTE.md. - Don't deploy, delete files, touch secrets or CI config, or call paid APIs. - When you're unsure, take the safest option, note it in NIGHT_NOTE.md, and keep going. Don't stop to wait for me. - When you're done, run the relevant tests. If you can't, write down why. - Finally, fill in NIGHT_NOTE.md: the branch name, what you did, how you tested it, what's still untested, and what you want to ask me in the morning.

morning/SKILL.md --- description: When I wake up, report on last night and list the questions for me disable-model-invocation: true disallowed-tools: AskUserQuestion --- I just woke up. Read NIGHT_NOTE.md first, then use git log to see what changed on last night's branch. If gh is installed, also check CI and new issues and PRs. Start with three to five sentences on what you did last night. Then list the questions I can answer right now, up to 5, numbered. Give each two or three options labeled A, B, C, and say which one you recommend and why. When I reply like "1A, 3B", do what I picked. If I say "the rest as recommended", do your recommendation for the rest. Don't touch anything I didn't mention.