Menu
Generate advanced and comprehensive .gitignore files based on project type, using stringent syntax for selecting and excluding files and directories.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Manage Obsidian vault frontmatter with rematter — validate schemas, sync to external destinations (Astro, etc.) with media options, rename fields, manage filenames. Load whenever performing bulk operations in Obsidian vaults (or other collections of markdown with frontmatter).
Use when asked to automate an action for OpenCode, for example run a formatter after edits, or running a script right before git commits, those are hooks and you should use this skill to implement them.
Guide the learner through a structured goal-setting exercise grounded in research on Mental Contrasting with Implementation Intentions (MCII). The exercise helps developers set concrete learning goals, visualize meaningful outcomes, anticipate realistic obstacles, and build if-then plans to overcome them.
Facilitates deliberate skill development during AI-assisted coding. Offers interactive learning exercises after architectural work (new files, schema changes, refactors). Use when completing features, making design decisions, or when user asks to understand code better. Supports the user's stated goal of understanding design choices as learning opportunities.
Generates a repo-specific orientation.md resource for the learning-opportunities skill. Only invoke via slash command (/orient:orient). Do not trigger automatically.
Use when asked to add or modify hooks for Claude Code specifically. Or, if the user is asking to automate an action, for example run a formatter after edits, or running a script right before git commits, those are hooks and you should use this skill to implement them.
| name | gitignore |
| description | Generate advanced and comprehensive .gitignore files based on project type, using stringent syntax for selecting and excluding files and directories. |
The GitHub CLI (gh) has a gh repo gitignore command that can be used to fetch templates from GitHub's collection. gh repo gitignore list will output the list of templates in GitHub's collection to stdout. When you have the name of the one you want, use gh repo gitignore view [TEMPLATE] to have the content output to stdout, which you can redirect to a .gitignore file or wherever you need it. This is the easiest way to spike out the boilerplate for a given project type.
The rest of the Skill covers manually adding entries in gitignore syntax for the specific project you're working in.
/path vs path/ vs path| Pattern | Meaning |
|---|---|
path/ | Matches a directory named path (and its contents) |
path | Matches both files AND directories named path |
/path | Matches path relative to the .gitignore file's location (anchored path) |
Examples:
build/ ignores the build directory and all its contentsbuild ignores any file or directory named build anywhere in the tree/build ignores only the build directory in the same folder as the .gitignoreGit uses fnmatch-style patterns:
| Pattern | Matches |
|---|---|
* | Any sequence of characters (except /) |
** | Any sequence of directories (including zero) |
? | Any single character |
[abc] | Any one character in the set |
[a-z] | Any one character in the range |
Examples:
*.log ignores all .log files**/node_modules ignores node_modules at any depthsrc/*.js ignores .js files directly in src/file?.txt matches file1.txt, file2.txt, etc.a/**/b matches a/b, a/x/b, a/x/y/b/**/b matches b anywhere in the tree| Pattern | Purpose |
|---|---|
!pattern | Negates — re-includes previously ignored files |
# | Comment line |
\ | Escape character for literal patterns |
Example:
# Ignore all .log files
*.log
# But not this specific one
!important.log