Our review
Adds specific files or patterns to .gitignore to prevent them from being tracked by Git.
Strengths
- Automates adding common patterns (logs, dependencies, builds).
- Checks if the file is already tracked and untracks it if needed.
- Adds explanatory comments for each entry.
Limitations
- Does not handle complex patterns or advanced globs.
- Does not update .gitignore if it's in a subdirectory.
- May require manual confirmation to avoid unintended exclusions.
Use this skill when you need to quickly ignore generated or sensitive files without deleting them.
Avoid this skill if you need to manage exclusions across multiple directory levels or prefer to set up global exclusions via git config.
Security analysis
SafeThe skill only uses standard git commands (git ls-files, git rm --cached) to manage .gitignore files. There is no destructive action, no network exfiltration, no obfuscated code, and no attempt to execute arbitrary commands or disable safety features.
No concerns found
Examples
Add node_modules/ to .gitignore and untrack it if already tracked.Add .env and .env.local to .gitignore with a comment explaining they contain secrets.Add dist/ folder to .gitignore and check if any files inside were already tracked.name: ignore description: 不要なファイル・ディレクトリを .gitignore に追加・管理する
Update Gitignore
This skill adds specific files or patterns to .gitignore to prevent them from being tracked by git.
Instructions
-
Check Status:
- Check if the file/directory is already in
.gitignore. - Check if the file is currently tracked by git using
git ls-files <path>.
- Check if the file/directory is already in
-
Update .gitignore:
- Append the path or pattern to the
.gitignorefile in the root directory. - Add a comment if necessary to explain why it's ignored.
- Append the path or pattern to the
-
Untrack (if needed):
- If the file was already tracked, run
git rm --cached <path>to stop tracking it while keeping the local copy.
- If the file was already tracked, run
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.