repo-ecosystem-hygiene

Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.

Repositorio: vamseeachanta/workspace-hub
Última actividad en el origen: 12 de junio de 2026 a las 17:40
Idioma detectado de SKILL.md: inglés
Estrellas: 16
Forks: 7

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/vamseeachanta/workspace-hub --skill repo-ecosystem-hygiene

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

communication-voice

Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name.

2026-07-30

hf-dataset-publishing

Save/publish analysis or computation results from ANY ecosystem repo to Hugging Face as a queryable, viewer-renderable dataset. Use when the user wants to "save results to hugging face", "publish dataset to HF", "hugging face data saving", "save analysis results", "hf dataset", "make results queryable", or "render via datasets-server API". Reshapes nested results into flat parquet tables, writes a dataset card with a viewer `configs:` block and provenance, applies license/public-vs-private routing, enforces a domain data-quality gate (faithful-to-source != correct), publishes to `aceengineer/<repo>-<projection>`, and verifies via the datasets-server API.

2026-07-28

github-repo-management

Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.

2026-07-23

Ver todos los de este repositorio

Repo Ecosystem Hygiene

Use this skill when reviewing .claude/state/repo-ecosystem-hygiene/latest.md or the matching JSON state.

Safety Boundary

The audit is read-only. It reports drift; it does not clean files, update branches, sync remotes, remove worktrees, or post GitHub comments. Treat every remediation action as a separate approved workflow.

Read The Latest Report

UV_CACHE_DIR=.claude/state/uv-cache bash scripts/cron/repo-ecosystem-hygiene-audit.sh sed -n '1,220p' .claude/state/repo-ecosystem-hygiene/latest.md

Triage Findings

ERROR on a required repo: verify the checkout/upstream state directly, then route through repo-sync or a GitHub issue if the fix needs approval.

WARN on optional or machine-access repos: preserve the evidence, then decide whether to sync, archive, or update config/workstations/registry.yaml.

dirty_worktree, ahead_of_upstream, or behind_upstream: run a direct git status --short --branch in that repo, preserve the output, then route through repo-sync or issue-scoped manual integration.

missing_upstream: do not invent tracking. Record the current branch and remotes, then decide whether the repo should track a remote branch or be marked differently in the registry.

stash_inventory or stale_stash: inspect git stash list --date=iso-strict, preserve any needed patch with an approved workflow, and only drop a stash after explicit disposition.

worktree_drift, stale_worktree, or stale_branch: use the worktree/branch hygiene workflow; never prune/delete from this audit.

registry_disposition_required: do not delete. Add a registry disposition or open an issue with the path, repo state, and recommended owner.

unknown_sibling_residue: identify owner/source first. If it is expected runtime state, add an explicit registry or runtime allowlist; otherwise open a cleanup issue.

registry_policy_gap: reconcile config/workstations/registry.yaml so raw machine access and governed buckets agree.

historical_state_changed_since_prior_comment: preserve the historical source issue/comment context and reconcile registry history before taking cleanup action.