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.
Pare e solicite confirmação antes de instalar.
Revise o plano e obtenha o consentimento explícito do usuário antes de alterar arquivos.
Instalar com meu Agente
Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.
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.Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.
Recursos legíveis por agentes
Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.
Testar
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.
Auditoria de segurança
Risco 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.
Preocupações de segurança confirmadas (1)
Fatores de risco
🌐 Acesso à rede (4)
⚙️ Comandos externos (26)
📁 Acesso ao sistema de arquivos (6)
🔑 Variáveis de ambiente (1)
Compartilhar e citar este relatório
Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.
Copiar link do relatório
https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/haoranyu-clean-closed-issue-worktrees?utm_source=security_passport_badge)Badge 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>Cartão incorporável
<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>Citações acadêmicas (APA · BibTeX · CFF)
Citação 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ção 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"
Pontuação do Skillstore
Por que esta pontuação Confiança das evidências: MédioO que você pode criar
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.
Teste estes 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.
Boas práticas
- 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.
Perguntas frequentes
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?
Detalhes do desenvolvedor
Autor
haoranyuLicença
MIT
Revisão da Skillstore
r1
Aviso de versão
O autor não declarou uma versão.
Referência
fc3130f4d3c7bcbf7ce69176507137d35adfc0d8
Atualidade da manutenção
30/08/2026
Uso
1 downloads · 1 visualizações
Estrutura de arquivos