メニュー
Create or update repository `.gitignore` rules, including pinned upstream template syncs. Use when changing ignored-file behavior or merging `github/gitignore` content.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Set up and use an isolated Git worktree for repository implementation tasks. Use unless the user explicitly requests another workspace arrangement.
Review or draft repository commit messages for Conventional Commits format, accurate change summaries, breaking-change footers, and required attribution trailers. Use before creating, amending, or validating a commit.
Maintain a canonical developer changelog and versioned release history. Use when adding or correcting Keep a Changelog entries, prerelease history, compatibility context, or release-source material; not for user-facing release notes or publishing.
Review implementation changes for readability, maintainability, design intent, and verification. Use for source code, tests, scripts, configuration, generated or vendored files, and dependencies; pair with security-check for security- or supply-chain-sensitive changes.
Review or revise explanatory prose for readability, local structure, audience fit, and preserved nuance. Use for wording in documentation, comments, release notes, issues, pull requests, changelogs, handoff notes, and Agent Skills after the document's purpose and factual ownership are known. Use software-documentation-maintenance instead for repository-wide document maps, canonical ownership, technical evidence, coverage, or migration.
Create or review channel-specific release notes from a canonical changelog. Use when checking destination history or publication readiness.
| name | gitignore-workflow |
| description | Create or update repository `.gitignore` rules, including pinned upstream template syncs. Use when changing ignored-file behavior or merging `github/gitignore` content. |
Inspect the repository state and current .gitignore. Separate project-specific rules from template-derived blocks.
Preserve project-specific rules unless the user explicitly requests their removal. Avoid broad patterns that could
hide source files; note that .gitignore does not untrack files already committed.
When syncing github/gitignore, use security-check and verify the repository, exact template path, and reviewed
commit hash before fetching or copying. Stop and report a blocker when provenance or a safe network path cannot be
verified.
Pin every copied template URL to its commit hash. Keep upstream blocks semantically unchanged, including intentional duplicates, and use a deterministic section order.
Use this pattern for each template:
# <TemplateName>.gitignore
# https://github.com/github/gitignore/blob/<commit-hash>/<TemplatePath>
{template content}
Validate the resulting behavior with git status --short and report changes affecting .env, lockfiles, build
artifacts, caches, or IDE folders.
Never put secrets or real environment values in comments. Keep agent-local directories explicit when needed, for example
.agents/worktrees/ and .agents/references/.