repo-hygiene

Inspect GitHub repository state and flag risks before commits, pushes, or pull requests.

Updated May 6, 2026
One-click install
npx skills add https://github.com/UnionStreetAI/unionstreet --skill repo-hygiene-unionstreetai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-hygiene
Source: https://github.com/UnionStreetAI/unionstreet/tree/main/plugins/github/skills/repo-hygiene
Command: npx skills add https://github.com/UnionStreetAI/unionstreet --skill repo-hygiene-unionstreetai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing a branch for commit, push, or pull request often hides risks like leaked secrets, unrelated changes, and lockfile drift that only surface during review or CI failures. ## Core Features & Use Cases - Branch State Inspection: Reviews git status, current branch, upstream, remotes, and changed files to build a complete picture of repository state. - Risk Detection: Flags accidental secrets, .env files, credential files, generated artifacts, lockfile drift, and unrelated changes before they reach a remote. - Commit and PR Drafting: Compares branch commits against the base branch and drafts commit messages or PR bodies grounded in the full diff. - Use Case: Before opening a pull request, run this Skill to confirm no .env file slipped in, group the changed files logically, and produce a draft PR body for maintainer review. ## Quick Start Check my current branch for risks and summarize what is ready to push as a pull request.

Frequently Asked Questions about repo-hygiene

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

FAQPage Schema
How do I check my git branch before creating a pull request?▼

Inspect git status, the current branch, upstream, remotes, and changed files, then compare branch commits against the base branch. This Skill automates that review and summarizes what is ready, what is risky, and what should be excluded.

How to detect secrets or .env files before pushing to GitHub?▼

Scan changed files for .env files, credential files, private keys, and machine-local config before staging or pushing. The Skill flags these as risk items and excludes them from commits unless explicitly instructed otherwise.

Can I use the gh CLI to create pull requests from any repository?▼

The gh CLI only works when the repository remote targets GitHub. This Skill confirms the remote points to GitHub before invoking gh, and prefers draft PRs until CI and review status are known.

What should I do about unrelated changes in my working tree?▼

Unrelated user changes should not be staged without explicit instruction. The Skill groups changed files and flags unrelated modifications so you can decide whether to exclude them from the commit.

When should I use a draft pull request instead of a regular one?▼

Use a draft PR when CI results and review status are not yet known. Draft PRs signal work in progress to maintainers and prevent premature merging while checks are still running.