latitude-repo-hygiene

Name: latitude-repo-hygiene
Availability: InStock
Author: joolbits

Prevent commits of generated artifacts and validate release branch cleanliness.

Updated Jan 29, 2026

Search Tags:#automation #git #release management #cleanup #gitignore #repo hygiene

Ready to run

npx skills add https://github.com/joolbits/latitude --skill latitude-repo-hygiene

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: latitude-repo-hygiene
Source: https://github.com/joolbits/latitude/tree/main/.windsurf/skills/latitude-repo-hygiene
Command: npx skills add https://github.com/joolbits/latitude --skill latitude-repo-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents accidental commits of generated artifacts, tooling folders, and other non-essential files, ensuring a clean and reliable repository for development and releases.

Core Features & Use Cases

Prevent Accidental Commits: Automatically identifies and flags forbidden files and directories that should not be part of the repository.
Enforce Release Branch Hygiene: Provides rules and checks to ensure that release branches are clean and free from pollution.
Automated Cleanup: Offers commands to remove generated artifacts and staged files, simplifying the cleanup process.
Use Case: Before merging a pull request or tagging a release, run this skill to ensure that build outputs, caches, or IDE configuration files are not included, preventing potential conflicts and confusion.

Quick Start

Run the cleanup commands to remove generated artifacts from the build directory.

Frequently Asked Questions about latitude-repo-hygiene

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

FAQPage Schema

How do I prevent accidental commits of build artifacts and tooling folders in git?▼

You can prevent accidental commits by enforcing repository hygiene rules that automatically identify and flag forbidden generated artifacts, tooling folders, and OS-specific files before they are committed to the repository.

What's the best way to automate cleanup of staged files before a release?▼

The best way to automate cleanup is to run dedicated commands that remove generated artifacts and staged files from your build directory. This validates release branches and ensures they remain free from pollution before tagging.

How do I validate release branches to ensure they are free from pollution?▼

Validating release branches involves applying specific rules and checks that enforce repository hygiene, ensuring the branch is completely free from generated artifacts and non-essential files before you merge or tag a release.

Why should I enforce repo hygiene before merging a pull request?▼

Enforcing repo hygiene before merging a pull request ensures that build outputs, caches, and IDE configuration files are not included, preventing potential conflicts and confusion while maintaining the integrity of the repository.

Can I automatically remove generated artifacts from the build directory without manual filtering?▼

Yes, you can automatically remove generated artifacts by running automated cleanup commands specifically designed to clear build outputs and staged files, simplifying the cleanup process without needing manual file filtering.