congiuluc/gitignore
skills/gitignore/SKILL.md
Generate and maintain .gitignore files for any tech stack: .NET, Java, Python, React, Angular, VS Code extensions, Docker, Azure, and full-stack combinations. Use when: scaffolding a new project, adding a new technology to an existing project, reviewing tracked files for accidental commits, or regenerating .gitignore after stack changes.
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add congiuluc/my-awesome-copilot gitignoreInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 1:22 PM4.3s2 files scanned
SKILL.md
- name:
- gitignore
- description:
- Generate and maintain .gitignore files for any tech stack: .NET, Java, Python, React, Angular, VS Code extensions, Docker, Azure, and full-stack combinations. Use when: scaffolding a new project, adding a new technology to an existing project, reviewing tracked files for accidental commits, or regenerating .gitignore after stack changes.
- argument-hint:
- Describe the tech stack or combination (e.g., .NET + React, Java + Angular, Python FastAPI, VS Code extension).
Gitignore
When to Use
- Scaffolding a new project and need a .gitignore tailored to the stack
- Adding a new technology or framework to an existing project
- Reviewing whether sensitive or generated files are accidentally tracked
- Regenerating .gitignore after changing build tools, IDEs, or cloud providers
- Combining multiple stacks (e.g., .NET API + React frontend + Docker + Azure)
Official Documentation
- gitignore Patterns
- github/gitignore Templates
Procedure
- Detect the project stack by scanning for marker files (see Stack Detection)
- Select the matching template(s) from
./samples/ - Compose a combined
.gitignoreby merging the relevant sections - Follow the conventions in gitignore patterns reference
- Always include the Common section (OS, IDE, environment)
- Verify no sensitive files (
.env, secrets, keys) are tracked - Add project-specific entries at the bottom under
## Project-specific
Stack Detection
| Marker Files | Stack | Sample |
|-------------|-------|--------|
| .csproj, .sln, global.json | .NET | .gitignore-dotnet.sample |
| pom.xml, build.gradle, build.gradle.kts | Java | .gitignore-java.sample |
| pyproject.toml, requirements.txt, Pipfile | Python | .gitignore-python.sample |
| vite.config.ts + react in package.json | React | .gitignore-react.sample |
| angular.json, @angular/core in package.json | Angular | .gitignore-angular.sample |
| .vscode/, package.json with @vscode/vsce | VS Code Extension | .gitignore-vscode-extension.sample |
| Dockerfile, docker-compose.yml | Docker | Included in all stack samples |
| azure.yaml, .azure/ | Azure (azd) | .gitignore-azure.sample |
For full-stack projects, merge the backend + frontend + infrastructure samples.
Composition Rules
When combining multiple templates:
- Start with the Common section (OS artifacts, IDE files, env files)
- Add the backend section (.NET / Java / Python)
- Add the frontend section (React / Angular)
- Add the infrastructure section (Docker, Azure, Terraform)
- Add a
## Project-specificsection at the bottom for custom entries - Remove duplicate patterns across sections
- Keep sections clearly labeled with
##headers for maintainability
Related Skills
congiuluc/vscode-extension
tools
VerifiedTrustedCommunity
Build VS Code extensions with TypeScript. Covers extension anatomy, activation events, commands, tree views, webview panels, language features, testing, and publishing. Use when: creating a new VS Code extension, adding commands/views/providers, building webview UIs, implementing language server features, testing extensions, or packaging for the marketplace.
SKILL.mdUpdated Apr 16, 2026
congiuluc/version-tracking
development
VerifiedTrustedCommunity
Track implementations, features, bugs, and releases in a versioning document. Use when: adding a commit, completing a feature, fixing a bug, or preparing a release. Automatically updates CHANGELOG.md following Keep a Changelog format and Semantic Versioning.
SKILL.mdUpdated Apr 16, 2026
congiuluc/testing-frontend
development
VerifiedTrustedCommunity
Write frontend tests using Vitest and React Testing Library. Use when: testing React components, hooks, user interactions, form submissions, accessibility assertions, or mocking API services.
SKILL.mdUpdated Apr 16, 2026
congiuluc/testing-frontend-angular
development
VerifiedTrustedCommunity
Write Angular frontend tests using Jasmine, Karma, and Angular TestBed. Use when: testing Angular components, services, pipes, directives, user interactions, form submissions, accessibility assertions, or mocking HTTP services.
SKILL.mdUpdated Apr 16, 2026