Gitignore Sync

gitignore-sync combines gitignore.io templates with your repo context to produce a cleaner `.gitignore` with fewer overlooked cases. It generates `.gitignore...

Security Scan

This skill is internally consistent: it uses the included script to detect repo tooling, fetch gitignore templates from gitignore.io (toptal), and update a managed block in .gitignore without requesting credentials or unusual system access.

Purpose & Capability

Name/description match the provided code and instructions. The script detects repo files, maps tokens to known templates, fetches canonical rules from the gitignore.io endpoint, and writes a managed block — all expected for a gitignore-sync tool.

Instruction Scope

SKILL.md restricts execution to scripts/update_gitignore.py and the script's behavior is limited to inspecting the target repo (file/folder presence), optionally fetching rules from the gitignore.io API, and writing/updating a managed block in .gitignore. It does not read unrelated system files or attempt to exfiltrate secrets.

Install Mechanism

No install spec; this is instruction-only plus a bundled Python script. There are no downloads or archive extraction during install. The script uses Python stdlib networking (urllib) to fetch templates at runtime.

Credentials

No environment variables, credentials, or config paths are requested. Network access to the gitignore.io (toptal) API is used to fetch templates, which is proportionate to the stated purpose.

Persistence & Privilege

Skill does not request always:true, does not modify other skills or global agent config, and only writes the repository's .gitignore managed block (expected scope).

Assessment

This skill appears to do only what it says: detect repository tooling, fetch gitignore templates from the gitignore.io endpoint (https://www.toptal.com/developers/gitignore/api) and update a managed block in .gitignore. Before running: (1) review the templates the tool will apply (use --dry-run) so you know what ignore rules will be inserted, (2) run it from the correct repository root (or pass --repo), and (3) if you have network restrictions or want to avoid remote fetches, use --rules-file for offline input. The script does not require credentials or access other system resources. If you need higher assurance, inspect the bundled scripts/update_gitignore.py yourself and prefer dry-run first.

Generate high-confidence .gitignore rules from real repo signals and gitignore.io, then update safely via a managed block so manual rules stay untouched.

Execution Rule

Use scripts/update_gitignore.py as the only execution path. Do not fetch from the API directly in ad-hoc commands. Do not manually compose or rewrite .gitignore when this skill is selected.

Workflow

1. Infer requested templates from the user prompt.
2. Detect likely templates from repository files and folders.
3. Run scripts/update_gitignore.py with --prompt-text and/or --services.
4. Let the script fetch combined template rules from https://www.toptal.com/developers/gitignore/api/<templates>.
5. Let the script write or update a managed block in .gitignore.
6. Preserve non-managed user sections in .gitignore.

Run

From the target repository root, run:

python3 <skill-path>/scripts/update_gitignore.py \
  --prompt-text "create .gitignore for flutter firebase vscode" \
  --repo .

Use explicit templates when the user names exact services:

python3 <skill-path>/scripts/update_gitignore.py \
  --services flutter,firebase,visualstudiocode \
  --repo .

Notes

• Prefer passing both --prompt-text and --services when available.
• Keep manual custom rules outside the managed block markers.
• Re-run safely; the script replaces only the managed block.
• Use --rules-file for offline/local testing when network access is blocked.