원클릭으로 Manus에서 모든 스킬 실행

yeet-docs

스타3

포크0

업데이트2026년 6월 27일 19:37

Use when user-facing CLI behavior, flags, workflows, README examples, website manual pages, or changelog entries need to be updated.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

yeetrun

yeetrun/yeet

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Yeet Docs

Use this skill when a change affects what users run or read.

Surfaces

Root README.md for quickstart and common examples.
website/docs/ for the user manual.
website/docs/changelog.mdx only for tagged releases.
CLI help metadata in pkg/cli/cli.go and cmd/yeet/cli.go.
Help reference: .codex/skills/yeet-cli/references/yeet-help-agent.md.

Rules

Keep examples generic and free of private hostnames or service names.
Keep changelog bullets user-facing and concise.
The latest changelog entry must stand alone for someone installing or upgrading. If a screenshot showed only that version, it should still answer "what changed for me?" without requiring prior-release context.
Never make release plumbing the changelog message: avoid bullets about git hashes, submodule pointers, source revisions, CI retries, tag repair, or website publication mechanics unless the user needs a concrete action.
For a corrective release that supersedes a bad tag or artifact, carry forward the actual user-facing changes into the new latest version. If needed, mark the prior version as superseded in plain user terms, but do not make the corrective mechanics the only bullet.
For CLI syntax changes, update parser tests, help text, README, and website docs together.
Commit website changes inside the submodule before committing the root submodule pointer.

Checks

git -C website diff --check
rg -n "private[-]host|/User[s]/" README.md website/docs .codex/skills

이 저장소의 다른 Skills

같은 저장소

yeet-cli

yeetrun/yeet

Use for yeet CLI operations like deploying or updating services, restarting/removing services, installing or upgrading catch on a host, checking status/logs/info, and guidance on CATCH_HOST/--host targeting.

2026-07-093

yeet-docker

yeetrun/yeet

Use when changing Docker compose deployment, docker pull/update/outdated behavior, internal registry image handling, Docker networking, or digest comparison logic.

2026-06-293

yeet-quality

yeetrun/yeet

Use when choosing verification commands, working on tests, quality tooling, race/fuzz/mutation checks, pre-commit failures, or release-quality gates.

2026-06-293

yeet-release

yeetrun/yeet

Use when preparing, validating, tagging, or pushing a yeet patch release.

2026-06-293

yeet-rpc

yeetrun/yeet

Use when changing yeet client command routing, catch remote execution, catchrpc types, or the boundary between local CLI parsing and catch-side parsing.

2026-06-293

name	yeet-docs
description	Use when user-facing CLI behavior, flags, workflows, README examples, website manual pages, or changelog entries need to be updated.

Yeet Docs

Use this skill when a change affects what users run or read.

Surfaces

Root README.md for quickstart and common examples.
website/docs/ for the user manual.
website/docs/changelog.mdx only for tagged releases.
CLI help metadata in pkg/cli/cli.go and cmd/yeet/cli.go.
Help reference: .codex/skills/yeet-cli/references/yeet-help-agent.md.

Rules

Keep examples generic and free of private hostnames or service names.
Keep changelog bullets user-facing and concise.
The latest changelog entry must stand alone for someone installing or upgrading. If a screenshot showed only that version, it should still answer "what changed for me?" without requiring prior-release context.
Never make release plumbing the changelog message: avoid bullets about git hashes, submodule pointers, source revisions, CI retries, tag repair, or website publication mechanics unless the user needs a concrete action.
For a corrective release that supersedes a bad tag or artifact, carry forward the actual user-facing changes into the new latest version. If needed, mark the prior version as superseded in plain user terms, but do not make the corrective mechanics the only bullet.
For CLI syntax changes, update parser tests, help text, README, and website docs together.
Commit website changes inside the submodule before committing the root submodule pointer.

Checks

git -C website diff --check
rg -n "private[-]host|/User[s]/" README.md website/docs .codex/skills