메뉴
Reference for pncli's cross-service CLI parameter conventions (currently --input-file). Use before adding a new flag, or when a command needs to accept a large/structured value, to check whether an existing pattern already fits instead of inventing a one-off.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/kolatts/pncli --skill conventions명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Use when asked to set up pncli, configure a service, initialize a repo, or run pncli commands. Walks through identity, work item tracking, source control, and optional services. For any specific service, read the included <service>.md file.
Open a PR for the current branch against main. GitHub only — for ADO/Bitbucket projects use /ship from the installed pncli skills instead. Runs the full pre-PR gate (build, lint, typecheck, tests, code review, docs) using parallel subagents before opening the PR. Use whenever the user says "open a PR", "create a PR", "ship this", "pull request", or "/ship".
SOC 직업 분류 기준
SKILL.md 표시 중
| name | conventions |
| description | Reference for pncli's cross-service CLI parameter conventions (currently --input-file). Use before adding a new flag, or when a command needs to accept a large/structured value, to check whether an existing pattern already fits instead of inventing a one-off. |
| providers | none |
| category | engineering |
| services | none |
Home for pncli-wide CLI parameter conventions — patterns that should be named and behave the same way in every service, not reinvented per command. Check here before adding a flag that might already have a pattern.
--input-file (long rich-text fields on ticket-shaped commands)Used today by jira create-issue/update-issue and ado work create/work update. Solves the original problem (Windows' ~32K command-line limit on inline text — #256) while staying decoupled from any org's custom fields.
{ <service-specific top-level keys>, fields: { <field-name-or-id>: <value> } }. - reads stdin.fieldMap, ADO fieldAliases); an unrecognized key with no whitespace (customfield_10032, MyOrg.SomeField) passes through untouched — no custom field needs pre-registering.@file value refs: any string value starting with @ is replaced with that file's contents (resolveAtFileRef in src/lib/input.ts) — keeps big fields (a Description, Acceptance Criteria) out of the JSON as literal text.--summary, --field, ...) overrides the same key from the file; overridden keys go to stderr (warn(...)) and to meta.overrides: string[] in the output.pncli <service> schema → { schema, example } (--example-only for just the example), so the shape is never doc-only.Reuse src/lib/input.ts (readJsonInputFile, resolveAtFileRef, mergeWithOverrides, resolveTextInput) rather than re-implementing file/stdin/override logic per service. Confluence is the one exception — a single large HTML body doesn't need a field dictionary, so create-page/update-page just take --body/--body-file.