Skip to content
cccskills
FreePublished on GitHub

public-hygiene-review

Review public repository changes for secrets, private paths, signing identities, bundle IDs, generated artifacts, local logs, and private workflow leaks.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

public-hygiene-review

Prevent private or unsafe material from entering public repositories.

Procedure

  1. Inspect staged, unstaged, and untracked files in the public repo scope.
  2. Build a risk list from changed paths and content: secrets, secret_ref bindings, paths, identities, governed connector context exports, bundle IDs, Team IDs, SKUs, signing fingerprints, package names, private URLs, approval/audit traces, logs, screenshots, caches, generated artifacts, brands, names, and workflow details.
  3. Search filenames, paths, textual content, and reasonable asset metadata.
  4. Classify findings as safe_public, false_positive, needs_user_decision, or must_remove_before_publish.
  5. Remove or isolate must_remove_before_publish findings before continuing.
  6. Run the repo hygiene checks and record limitations.

Constraints

  • Do not resolve uncertainty by publishing the private value.
  • Do not assume a staged change is safe.
  • Treat private governed-context envelopes as protected handoff artifacts, not public repo material.
  • Treat governed context audit and approval metadata as public only when it contains no private identifiers, plaintext secrets, provider credentials, or maintainer-local details.
  • Keep private commit-manager, signing, launcher, and local-device procedures out of public docs.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Govern Clawix accessibility changes across screen reader behavior, keyboard navigation, focus order, contrast, reduced motion, text scaling, timed interactions, and agent-generated UI.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Review or update stable, canonical, any-human, PMF, and adoption claims using adoption/canonicity governance packets.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Turn a new or changed ADR into implemented behavior, routing docs, tests, and guardrails rather than leaving it as standalone prose.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Repair confirmed architecture drift in small batches while preserving public canon and avoiding broad opportunistic refactors.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Given an existing Style, generate a human-readable brand guidelines document covering colors, typography, voice, do/don't, imagery rules, and usage examples. Use when the user asks for a brand book, brand guide, or design system document.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Add or improve canonical data catalog collections, fields, aliases, relations, evidence tags, docs, and tests.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

See all skills by clawic

Report a problem with this skill