프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. Google로 로그인하면 리뷰를 쓸 수 있어요.프로토타입 · 30분마다 업데이트
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

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에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/kunchenguid-gnhf.svg)](https://mcp.popnx.com/en/skills/kunchenguid-gnhf)

비슷한 Skill

같은 종류의 작업, Skill 목록과 같은 순서

비슷한 항목과 비교
이 항목
gnhf
skillsnacosanatomyleon
제작자kunchenguidvercel-labsalibabawheresryan22leon-ai
Skill 수11111
GitHub 별4,27839,77833,52427,79917,688
마지막 코드 변경2026년 11월 17일2026년 11월 17일2026년 11월 17일2026년 10월 19일2026년 11월 13일
라이선스MITMITApache-2.0MITMIT

kunchenguid의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요

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 1Claude Code에게 설치 맡기기

이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요

Where to install
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) for all my projects, at ~/.claude/skills/gnhf. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) into the project this chat is open in (at .claude/skills/gnhf). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. 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
  3. Claude Code를 다시 열고 /gnhf를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요

직접 설치한 Skill은 ChatGPT 데스크톱 앱, Codex CLI, IDE의 Codex 확장 프로그램에서 쓸 수 있습니다 · 웹과 모바일의 ChatGPT에서는 직접 설치한 Skill을 쓸 수 없고 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다

ChatGPT 데스크톱 앱

ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다

Option 1ChatGPT에게 설치 맡기기

ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요

Where to install
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) for all my projects, at ~/.agents/skills/gnhf. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) into the project this chat is open in (at .agents/skills/gnhf). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. 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만 쓸 수 있습니다

이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요

Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com

Option 1Codex에게 설치 맡기기

이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다

Where to install
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) for all my projects, at ~/.agents/skills/gnhf. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) into the project this chat is open in (at .agents/skills/gnhf). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. 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
  3. Codex를 다시 열고 관련 작업을 요청하면 Codex가 skill을 목록에 보여 줘요

Option 1Cursor에게 설치 맡기기

이 문장을 복사해 Cursor 채팅에 붙여 넣으세요

Where to install
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) for all my projects, at ~/.cursor/skills/gnhf. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) into the project this chat is open in (at .cursor/skills/gnhf). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.

  1. 터미널 열기

    Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요

  2. 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
  3. Cursor Agent 채팅에서 /를 입력하고 gnhf 선택

Option 1Let the AI install it

Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · Copy this sentence into the app’s chat

Where to install
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) for all my projects, at ~/.claude/skills/gnhf (in Codex use ~/.agents/skills/gnhf, in Cursor ~/.cursor/skills/gnhf). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill gnhf from https://github.com/kunchenguid/gnhf folder skills/gnhf (commit bfd97af) into the project this chat is open in (at .claude/skills/gnhf; in Codex use .agents/skills/gnhf, in Cursor .cursor/skills/gnhf). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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

Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.

GitHub에서 보기 ↗

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

토론

질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.

아직 글이 없어요. 처음으로 질문하거나 공유해 보세요.

이곳의 글은 사용자가 쓴 것으로, PopNx 팀의 글이 아니에요.

로그인하고 글쓰기

GitHub 정보

GitHub 스타
4,278
제작자
kunchenguid
라이선스
MIT
최근 코드 수정
2026년 11월 17일
repo 안 SKILL.md(번역본과 템플릿 포함)
1