메뉴
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 직업 분류 기준
Select a reviewed APM CLI version, then set up, pin, deploy, audit, and update APM-managed agent dependencies safely. Use when creating or editing apm.yml or apm.lock.yaml, choosing or installing APM, adding an Agent Skill, plugin, or MCP dependency, validating a pinned deployment, or preparing a cooldown-aware update proposal.
Set up and use an isolated Git worktree for repository implementation tasks. Use unless the user explicitly requests another workspace arrangement.
Review or create a BepInEx Mono mod for C# project and module structure, plugin identity, game compatibility, dependency boundaries, repository-family alignment, GitHub CI and release automation, package readiness, release metadata, and verification. Use when implementing, reviewing, preparing a release for, diagnosing quality gaps in, or applying a minimal-difference peer rollout to a BepInEx 5 Mono plugin or its build and release workflow.
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.
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/.