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

cli-output-and-safety

스타0

포크0

업데이트2026년 4월 23일 11:28

Use when working on cmd/piv or internal/cli/app, especially for commands, flags, formatting, JSON output, trace routing, config handling, or destructive-operation safety. Helps keep stdout/stderr contracts stable and preserves dry-run and confirmation behavior.

설치

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

Manus에서 실행

출처

PeculiarVentures

PeculiarVentures/piv-go

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

다운로드

Manus에서 실행

CLI Output And Safety

Use this skill when the task changes CLI behavior, output shape, or operator safety.

Workflow

Identify whether the change belongs in cmd/piv/ wiring or internal/cli/app/ behavior.
Check whether the command supports --json, tracing, config defaults, prompts, or destructive mutations.
Preserve the output contract:
- JSON goes to stdout only
- warnings, prompts, summaries, and trace lines go to stderr
For state-changing commands, verify whether --dry-run, --yes, and --non-interactive behavior must be updated together.
Add or update command-level tests before finishing.

Repo Patterns

Root and global flag wiring lives in cmd/piv/root.go.
Rendering and error output live in internal/cli/app/formatter.go.
Confirmation planning lives in internal/cli/app/planner.go.
Config-backed defaults live in internal/cli/app/config.go and related helpers.

Test Expectations

Prefer tests similar to cmd/piv/cli_test.go.
Assert stdout and stderr separately.
For JSON commands, unmarshal the envelope and assert the result payload instead of comparing raw strings.

이 저장소의 다른 Skills

같은 저장소

adapter-vendor-workflows

PeculiarVentures/piv-go

Use when changing adapters, adapter runtime resolution, vendor-specific token behavior, capability reporting, initialization/reset flows, or built-in adapter registration. Helps keep vendor logic in the right package and aligned with emulator-backed tests.

2026-04-230

emulator-test-authoring

PeculiarVentures/piv-go

Use when adding or updating emulator-backed tests, APDU trace fixtures, fake reader contexts, or command tests that should avoid real hardware. Helps align new tests with the repository's existing emulator and trace patterns.

2026-04-230

git-commit-workflow

PeculiarVentures/piv-go

Use when the task involves preparing, reviewing, staging, or committing repository changes. Helps keep commits focused, avoids bundling unrelated diffs, and keeps commit messages consistent with the repository's expected style.

2026-04-230

name	cli-output-and-safety
description	Use when working on cmd/piv or internal/cli/app, especially for commands, flags, formatting, JSON output, trace routing, config handling, or destructive-operation safety. Helps keep stdout/stderr contracts stable and preserves dry-run and confirmation behavior.

CLI Output And Safety

Use this skill when the task changes CLI behavior, output shape, or operator safety.

Workflow

Identify whether the change belongs in cmd/piv/ wiring or internal/cli/app/ behavior.
Check whether the command supports --json, tracing, config defaults, prompts, or destructive mutations.
Preserve the output contract:
- JSON goes to stdout only
- warnings, prompts, summaries, and trace lines go to stderr
For state-changing commands, verify whether --dry-run, --yes, and --non-interactive behavior must be updated together.
Add or update command-level tests before finishing.

Repo Patterns

Root and global flag wiring lives in cmd/piv/root.go.
Rendering and error output live in internal/cli/app/formatter.go.
Confirmation planning lives in internal/cli/app/planner.go.
Config-backed defaults live in internal/cli/app/config.go and related helpers.

Test Expectations

Prefer tests similar to cmd/piv/cli_test.go.
Assert stdout and stderr separately.
For JSON commands, unmarshal the envelope and assert the result payload instead of comparing raw strings.