What it does
Before I go to bed, I tell my agents: good night, have fun
- Connects Instruction files the AI reads, with steps that call an outside service
- Account or key Some steps need a key for CURSOR_API_KEY (per the README)
- Category 自动化与智能体
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/kunchenguid-gnhf)相似的 Skill
同类工作,排序与 Skill 列表相同
Skill 和 MCP 有什么不同
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
适用的应用
CodexCursorGitHub CopilotOpenCode
依据开发者 README 和 repo 中的文件夹
安装
Is it safe?
- Who made it
GitHub account kunchenguid (person), 13 years old
- Use and upkeep
★ 4,278 stars · code last changed 2026年11月17日
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit bfd97af (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (205). Use "Let the AI install it" instead
Option 1让 Claude Code 帮你安装
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /gnhf,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.claude/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/kunchenguid/gnhf.git /tmp/popnx-skill-kunchenguid-gnhf-bfd97af && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-kunchenguid-gnhf-bfd97af/skills/gnhf' ~/.claude/skills/gnhf重新打开 Claude Code,输入 /gnhf,或直接提出相关任务,Claude 会自动选用
ChatGPT 桌面应用
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
Option 1让 ChatGPT 帮你安装
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2自己放入文件夹
把 gnhf 文件夹放到 ~/.agents/skills/gnhf
~ 是你的主文件夹($HOME)
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/kunchenguid/gnhf.git /tmp/popnx-skill-kunchenguid-gnhf-bfd97af && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-kunchenguid-gnhf-bfd97af/skills/gnhf' ~/.agents/skills/gnhf
安装之后
- ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
- 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
- Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
网页版和手机版 ChatGPT
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1让 Codex 帮你安装
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/kunchenguid/gnhf.git /tmp/popnx-skill-kunchenguid-gnhf-bfd97af && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-kunchenguid-gnhf-bfd97af/skills/gnhf' ~/.agents/skills/gnhf重新打开 Codex 并提出相关任务,Codex 会列出这个 skill
Option 1让 Cursor 帮你安装
复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 gnhf
Checked against official docs 2026年11月12日 · Source: cursor.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.cursor/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/kunchenguid/gnhf.git /tmp/popnx-skill-kunchenguid-gnhf-bfd97af && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-kunchenguid-gnhf-bfd97af/skills/gnhf' ~/.cursor/skills/gnhf在 Cursor 的 Agent 聊天中输入 / 并选择 gnhf
Option 1Let the AI install it
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月17日
查看原始 SKILL.md
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: gnhf
description: Use when the user asks to run GNHF, says they are going to sleep or leaving and wants an agent-managed coding run, asks to supervise, steer, or review an active GNHF run, or gives feedback on GNHF results.
---
# GNHF
## Overview
GNHF is an agent orchestrator: it repeatedly calls another coding agent until a natural-language stop condition is met. This skill teaches the host agent to prepare one durable run and, in Companion mode, steer or review it.
Core rule: the host agent orchestrates; GNHF executes. Do not manually implement inside the same scope while a GNHF worker is responsible for it unless the user explicitly changes the delegation.
In Companion mode, GNHF completion is not user acceptance. "Stop condition met" only means the worker stopped; the host still compares the result to the user's latest requirements and fresh verification.
## Modes
Choose exactly one mode for the run.
### Hands-Off
Use when the task is bounded, verification is clear, and the user wants one configured run to proceed without steering.
- Prepare a precise prompt with constraints, non-goals, verification, and stop condition.
- Launch GNHF and wait for completion.
- Intervene early only for hard failure, runaway scope, destructive behavior, or impossible prerequisites.
- Report the final GNHF status after exit.
Examples:
- English: "I'm going to bed. Use GNHF with Copilot to keep working on this branch and stop when the test suite passes."
- Chinese: "我要睡了。用 GNHF 接着跑这个分支,测试都过了就停。"
### Companion
Use when the task is uncertain, exploratory, design-heavy, research-heavy, or likely to need course correction.
Default to Companion when the user asks to iterate until satisfied, requests multi-round work, provides review findings, asks for design/skill/documentation improvement, or asks for supervision.
- Keep a note of original intent, branch, session id, and last known result.
- Poll the active GNHF process until exit or until an intervention point appears.
- Intervene when the worker optimizes the wrong thing, repeats failed fixes, skips requested research, drifts scope, or claims success without evidence.
- Treat review findings as the next acceptance criteria.
- Prefer a new bounded GNHF prompt over manually taking over implementation.
Examples:
- English: "Run GNHF for a few rounds on this onboarding flow. Check the diff between rounds and tighten the next prompt if it starts polishing the wrong thing."
- Chinese: "用 GNHF 多跑几轮这个 onboarding 流程。每轮看一下 diff,如果它开始改偏了,就收窄下一轮 prompt。"
## Launch
Check the installed CLI before relying on flags:
```bash
gnhf --help
```
Known shape:
```bash
gnhf \
--agent <agent> \
--max-iterations <n> \
--stop-when "<observable completion condition>" \
--prevent-sleep on \
"<worker prompt>"
```
Use `--model <model>` to select a model for a run. For config defaults and agent-specific restrictions, follow the README [Configuration](../../README.md#configuration).
Before launch:
```bash
git status --short
git branch --show-current
git log --oneline --max-count=5
```
Prompt skeleton:
```text
Objective: <one concrete outcome>.
Use <agent/model requirement>. Work in this repo. Treat this as a long-running GNHF task.
Before coding, inspect the current repo, relevant docs, and recent commits. Preserve user changes. Do not make unrelated refactors.
After each meaningful slice, run relevant verification. If blocked, commit no fake success; leave notes with the blocker and evidence.
Stop only when: <observable completion condition>.
```
## Steer
In Companion mode, evaluate after each iteration or meaningful output chunk:
| Signal | Action |
| ------------------------------------------------------------- | -------------------------------------------------------------------- |
| Worker found a real blocker | Stop or relaunch with blocker-specific instructions |
| Good partial slice | Let it continue or tighten the next stop condition |
| Skipped requested research | Relaunch with research as explicit first deliverable |
| Worker changes unrelated files | Stop and review before continuing |
| Worker claims success without verification | Review immediately; relaunch only with evidence-based stop condition |
| Reviewer finds a blocking issue or user says not satisfactory | Relaunch with that finding as the sole bounded correction |
Steering prompt:
```text
Continue from the current repo state. The previous run partially succeeded: <evidence>.
Do not redo completed work. Focus only on <bounded correction>.
The issue to fix now is <specific observed issue>. Verify with <commands/checks>.
Stop only when <observable condition>.
```
## Companion Review
Use only in Companion mode, when the host is supervising quality or deciding whether to continue with another bounded run.
1. Inspect branch, status, commits, changed files, and diff.
2. Read GNHF notes/logs as claims, not evidence.
3. Run independent verification: tests, lint, build, typecheck, manual QA, or domain-specific checks.
4. Compare the result to the stop condition and the user's latest feedback.
5. Decide: **Mergeable**, **Needs follow-up GNHF run**, or **Do not merge**.
If the result needs follow-up, continue in Companion mode instead of presenting the run as complete. Do not merge unless explicitly authorized.
## Findings
Use when the user provides findings such as "not preserved", "scope drift", "missing requirement", or "why did you stop".
1. Treat the run as Companion mode.
2. Convert each finding into an observable correction. Preserve severity, file/line scope, and the user's wording.
3. Relaunch on the same candidate branch when salvageable.
4. Prompt the worker to fix only the bounded finding, preserve completed valid work, verify, and stop only when the finding is no longer true.
5. Review again after the follow-up.
6. Repeat until no blocking findings remain, verification passes, or a real blocker is found.
## Morning Review
Use when the user returns with "good morning", "how did last night's run go?", or similar after a GNHF run.
Do not ask what to review first. Reconstruct state:
```bash
git status --short
git branch --show-current
git log --oneline --decorate --max-count=20
pgrep -fl 'gnhf|claude|codex|copilot|cursor-agent|opencode|rovodev' || true
```
Inspect likely GNHF branches, notes, logs, terminal sessions, and changed files. If a GNHF process is still running, report that first.
Report mode, agent, branch, status, changes, verification, stop-condition result, quality assessment, and recommended next action. Never summarize an overnight run from memory.
## Agent
The supported `--agent` roster comes from `gnhf --help`; the [Agents table](../../README.md#agents) in the GNHF README owns per-agent requirements. Do not hard-code the roster.
- Default to the agent the user explicitly requested, or the one already configured and authenticated locally.
- `codex`: repo-aware code work or review-heavy tasks.
- `claude`: reasoning-heavy implementation or prose-heavy planning when configured.
- `acp:<target>`: when the user wants to drive a custom ACP-compatible agent through GNHF.
## Safety
- Preserve user changes. Never run destructive git commands to clean up a GNHF branch.
- In Companion mode, do not trust a worker's success summary without fresh verification.
- Keep prompts outcome-based and evidence-based.
- Use concrete stop conditions. Bad: "looks good". Good: "the target workflow succeeds, relevant checks pass, and no unrelated files changed."
- If the user is away, produce branches and a status report, not irreversible changes讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
来自 GitHub
- GitHub 星标
- 4,278
- 开发者
- kunchenguid
- 许可证
- MIT
- 最近代码更新
- 2026年11月17日
- repo 中的 SKILL.md 文件(含译本和模板)
- 1
- Repo
- kunchenguid/gnhf