菜单
Sync and harden command permissions between .claude/settings.json and .codex/rules/default.rules in this dotfiles repo.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | permission-sync |
| description | Sync and harden command permissions between .claude/settings.json and .codex/rules/default.rules in this dotfiles repo. |
このドキュメントは、./.claude/settings.json と ./.codex/rules/default.rules を
安全性を維持しつつ双方向同期するための正本手順です。
settings.json と default.rules の差分をなくしたいsed -n '1,260p' ./.claude/settings.json
sed -n '1,260p' ./.codex/rules/default.rules
python3 *, npm *, pnpm *, cargo *, git checkout:*, git commit:*, git stash:*, brew bundle:* は除外対象settings.json は Bash(...) 形式、default.rules は prefix_rule(...) 形式なので、同じ意味に正規化して比較するBash(ps:*) <-> prefix_rule(pattern=["ps"], decision="allow")Bash(git diff:*) <-> prefix_rule(pattern=["git", "diff"], decision="allow")jq empty ./.claude/settings.json
sed -n '1,260p' ./.codex/rules/default.rules
auth.json や sessions など機密/履歴は管理対象にしないbasic -> git -> gh -> brewsettings.json のセクションコメント（// basic, // git, // gh, // brew）は維持するPrevent dev-environment values (origins, ports, hosts, absolute paths, secrets) from leaking into build artifacts, generated code, or production output. Use whenever writing or reviewing build scripts / codegen, adding a URL / port / hostname / origin literal, branching on dev vs prod, configuring CORS or crossorigin attributes, or when generated files (*.gen.*, dist output, feeds, sitemaps) embed any absolute URL. Trigger proactively — this class of bug ships silently and is only noticed in production.
Working discipline for hard tasks — decompose, verify, and decide what to do next. Use whenever a task is non-trivial: the approach is not obvious, it spans multiple steps or files, it involves debugging an unknown cause, an irreversible or production-facing change, or the user says it is hard/complex/stuck. Also use when starting work that a strong model (Opus 4.8+) is delegated precisely because it is difficult. Do not wait for the user to ask for "planning" — apply this protocol proactively at the start of any such task.
Audit alignment between AGENTS.md and repo-local shared skills under .agents/skills. Invoke explicitly only; do not auto-trigger on generic agent or skill maintenance requests.
Create and iterate on implementation plans under .agents/plan/ so multiple agents (Claude / Codex / 他) can review each other's drafts. Use when entering plan mode, drafting an implementation plan, or reviewing an existing plan.
Create install scripts under ./install/install-<name>.sh following this dotfiles repo's build/install conventions (brew vs self-build, pkg/local layout, OS branching).