gitignore-check

Identify missing .gitignore patterns and propose ignore rules before commits.

2|Updated Apr 6, 2017
One-click install
npx skills add https://github.com/shiiman/dotfiles --skill gitignore-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitignore-check
Source: https://github.com/shiiman/dotfiles/tree/main/ai/codex/skills/gitignore-check
Command: npx skills add https://github.com/shiiman/dotfiles --skill gitignore-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

コミット前に .gitignore に追加すべきファイルをチェックし、機密情報や不要なファイルが誤ってコミットされるのを防ぎます。

Core Features & Use Cases

  • プリコミットチェック: 現在のステージングと作業ツリーを分析し、追加すべき .gitignore パターンを提案します。
  • 実務的な修正提案: よく使われるパターン(envファイル、ログ、ビルド成果物など)を除外候補として提示します。
  • Use Case: プルリクエストが頻繁に発生するチームで、コミット前にこのチェックを実行して機密情報の混入を防ぎます。

Quick Start

コミット前に不足している .gitignore パターンを特定し、推奨の ignore ルールを適用します。

Frequently Asked Questions about gitignore-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check .gitignore entries before committing to prevent sensitive files from being committed?

To check .gitignore entries before committing, analyze the staging area and working tree to identify missing ignore patterns for sensitive files like environment secrets, logs, and build artifacts, then apply a recommended ignore plan.

What files should be added to .gitignore patterns for a secure version control workflow?

Essential .gitignore patterns for secure version control include environment files, cryptographic keys, log files, and OS-specific artifacts to prevent unnecessary or sensitive data from entering the repository history.

Does pre-commit .gitignore sanity checking work for software projects of any size?

Pre-commit .gitignore sanity checking is applicable to software projects of any size, especially those containing environment secrets, logs, or build artifacts that require protection from accidental version control commits.

What is the best way to propose updates to .gitignore entries for environment secrets and logs?

The best way to propose .gitignore updates is to scan the working tree for common sensitive patterns like env files and logs, then output a recommended ignore plan with practical correction proposals before the commit occurs.

Can I generate a recommended ignore plan for OS artifacts and build artifacts before a pull request?

Yes, you can generate a recommended ignore plan by analyzing the working tree for OS artifacts and build artifacts, proposing specific .gitignore updates to prevent these unnecessary files from being committed during frequent pull requests.