clean-closed-issue-worktrees
Clean Closed-Issue Git Worktrees Safely
Completed issue worktrees consume disk space and leave stale Git registrations. This skill audits candidates and removes only explicitly confirmed targets after safety checks.
Detente y solicita confirmación antes de instalar.
Revisa el plan y obtén el consentimiento explícito del usuario antes de modificar archivos.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "clean-closed-issue-worktrees" from https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees.md and its manifest at https://skillstore.io/api/skills/haoranyu-clean-closed-issue-worktrees/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "clean-closed-issue-worktrees". Scan my repository and find worktrees linked to closed issues.
Resultado esperado:
- Recommended: /workspace/project-1459, issue 1459 closed, clean, inactive, and retained by a remote branch.
- Keep: /workspace/project-1510, issue 1510 remains open.
- Needs review: /workspace/project-1402 contains an unapproved ignored environment file.
Usando "clean-closed-issue-worktrees". Prepare cleanup for the two recommended worktrees and retain branches.
Resultado esperado:
Prepared a two-target plan that retains both branches. Review the exact paths and confirmation identifier before execution.
Usando "clean-closed-issue-worktrees". Remove the confirmed targets.
Resultado esperado:
Removed both confirmed worktrees, retained their branches, deleted the temporary plan, and reported the estimated reclaimed space.
Auditoría de seguridad
Riesgo altoThe static findings are false positives caused by documentation examples, Markdown backticks, safety glob names, and argument-vector subprocess calls. However, execute accepts an editable plan without authenticating its origin and omits several create-plan policy checks, enabling bypass of approval safeguards.
Preocupaciones de seguridad confirmadas (1)
Factores de riesgo
🌐 Acceso a red (4)
⚙️ Comandos externos (26)
📁 Acceso al sistema de archivos (6)
🔑 Variables de entorno (1)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/haoranyu-clean-closed-issue-worktrees/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/haoranyu-clean-closed-issue-worktrees.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
haoranyu. (2026). clean-closed-issue-worktrees security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees/audits/1Cita BibTeX
@techreport{haoranyu-haoranyu-clean-closed-issue-worktrees-2026,
author = {haoranyu},
title = {clean-closed-issue-worktrees security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "clean-closed-issue-worktrees security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "haoranyu"
date-released: "2026-08-30"
url: "https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees/audits/1"
identifiers:
- type: other
value: "skillstore:haoranyu-clean-closed-issue-worktrees:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Reclaim Developer Disk Space
Audit old feature worktrees, review exact candidates, and remove approved directories while keeping local branches.
Maintain Shared Build Hosts
Find completed issue worktrees while preserving active, dirty, locked, or uncertain environments.
Close Repository Maintenance Cycles
Verify GitHub or GitLab completion evidence before cleaning branches and worktree registrations.
Prueba estos prompts
Scan the repository at [repository path]. Show every worktree and do not remove anything.
Match worktrees in [repository path] to closed items from [GitHub or GitLab URL]. Recommend safe candidates and explain every exclusion.
Prepare a cleanup plan for [exact paths]. Keep branches, show ignored-path risks, and ask for confirmation before creating the plan.
Audit [repository path] against [baseline]. Propose backup branches for orphan commits and safe branch deletion only after ancestry verification.
Mejores prácticas
- Run the inventory from outside every possible removal target.
- Verify each issue or change through an authoritative provider route immediately before execution.
- Keep branches by default and review sensitive or unknown ignored paths explicitly.
Evitar
- Do not treat a scan request as approval to remove worktrees.
- Do not infer issue identity from directory numbers or title similarity alone.
- Do not use forced worktree or branch deletion commands.
Preguntas frecuentes
Does this skill remove worktrees during a scan?
Does it support GitHub and GitLab?
Will it delete local branches?
How are ignored files handled?
Can it clean active or dirty worktrees?
What happens when execution fails?
Detalles del desarrollador
Autor
haoranyuLicencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Ref.
fc3130f4d3c7bcbf7ce69176507137d35adfc0d8
Actualidad del mantenimiento
30/8/2026
Uso
1 descargas · 1 vistas
Estructura de archivos