메뉴
Inspect the current chezmoi sync state and report unapplied changes, unmanaged files, and whether it is safe to run chezmoi apply.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Intent-Driven Development (IDD) に基づき、ADR（Architecture Decision Record）形式の Intentドキュメントを作成するスキル。ユーザーの「こういう機能を作りたい」「この設計判断をした」 という意図をWhy/Whatに整理し、How（実装詳細）の混入を検出・分離して、docs/adr/ に連番の ADRファイルを生成する。 このスキルは以下の場合に必ず使用すること： - ユーザーが /intent と入力したとき - 「ADRを書きたい」「意図を記録したい」「intentを作成」「設計判断を残したい」「ADR作って」 「決定を記録」「なぜこうしたか残しておきたい」などと言ったとき - ユーザーが新機能やアーキテクチャの判断について議論し、それを文書化したいと示唆したとき Do NOT trigger for: バグ修正の記録、ルーチンなリファクタリング、意図が自明な些細な変更。
Automatically generate PR descriptions according to project templates.
Structured 5W1H completeness checker for written communication. Analyzes text using a Who/What/When/Where/Why/How framework, produces a status table for each element, and provides concrete rewrite suggestions for missing information. ALWAYS use this skill when the user shares text and asks you to review it, check it, proofread it, or confirm it's ready to send — including progress reports, daily standups, meeting minutes, incident reports, handoff documents, status updates, client emails, Slack messages, PR descriptions, or any prose meant to inform others. Also trigger when the user says things like "これで大丈夫か", "情報足りてるか", "抜けてないか", "伝わるかな", "5W1H", "check if anything is missing", "is this clear enough", "review before sending", or asks you to check whether a written message has enough context for the reader. This skill adds a structured framework that generic reviewing lacks — do not skip it just because you could review text without it. Do NOT trigger for: code review, security review, grammar/style-only che
Review a draft text (message, report, PR description, commit message, etc.) from the reader's perspective and suggest improvements.
Safely add a new dotfile to chezmoi management, determining the correct prefix and committing the result.
Scan chezmoi source files for accidentally exposed secrets and verify sensitive files have the private_ prefix.
| name | sync-status |
| description | Inspect the current chezmoi sync state and report unapplied changes, unmanaged files, and whether it is safe to run chezmoi apply. |
Provide a clear overview of the current chezmoi state and guide the user through safely applying any pending changes.
Run all of these in parallel:
# Summary of managed file states
chezmoi status
# Detailed diff of what would change on apply
chezmoi diff
# Git status of the source directory
git -C ~/.local/share/chezmoi status
# Recent commits in the source repo
git -C ~/.local/share/chezmoi log --oneline -5
chezmoi status OutputEach line has a two-character status code. Explain relevant entries to the user:
| Code | Meaning |
|---|---|
A | File is managed but missing from target — will be created |
M | Source and target differ — target will be updated |
D | File removed from source — will be deleted from target |
R | File permissions differ |
chezmoi applyFlag concerns before applying:
git -C ~/.local/share/chezmoi fetch && git status to checkIf the user wants to know what config files exist on the system but are NOT managed by chezmoi:
# Common config locations to audit
ls ~/.config/
ls ~/
Compare against chezmoi managed output and highlight candidates worth adding.
If there are no concerns, offer to apply:
chezmoi apply --verbose
Then verify:
chezmoi status # should show no remaining differences
If the source directory has uncommitted edits, prompt the user to commit:
git -C ~/.local/share/chezmoi status
git -C ~/.local/share/chezmoi add <files>
git -C ~/.local/share/chezmoi commit -m "chore: sync dotfiles"
Produce a structured summary:
## chezmoi Sync Status
### Pending Changes (N files)
- Modified: ...
- Added: ...
- Deleted: ...
### Source Repo Git State
- Branch: main (clean / N uncommitted changes)
- Remote: up to date / N commits behind
### Safety Assessment
- ✅ Safe to apply / ⚠️ Review before applying
### Recommended Next Steps
1. ...
$ARGUMENTS