cleanup-workspace
Clean up the local workspace after a dev branch has been merged into main. Verifies the current dev branch is fully merged into origin/main, then switches to main, pulls the latest, deletes the local dev branch, and deletes the remote dev branch if it still exists. STOPS and warns the user if the cu
v2026.11.13-dcf20203 instalações+3 em 7 dias67 EstrelasMITsincronizado há 11 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install hlnd2t/cleanup-workspaceGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote13320dfc…325ce1bd
13320dfc2a87…cba8325ce1bd2 arquivos · 2.1 KBVarreduraMédio1 achado
- injection.no_confirmationSKILL.md:71
Fontegithub.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/cleanup-workspace@dcf2020
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
Post-merge housekeeping: verify the active dev branch landed in main, then prune it locally and on origin.
When to Use
After a pull request authored on a dev* branch has been merged into main and the user wants to return the workspace to a clean state on the updated main branch.
Safety Rules
- NEVER delete a branch that is not fully merged into
origin/main. If the merge check fails, STOP immediately and report to the user — do not pass-Dto force delete. - NEVER run on
mainitself. If the current branch ismain, abort with a clear message. - NEVER discard uncommitted changes. If the working tree is dirty, abort and ask the user to commit or stash first.
- The remote name is assumed to be
origin. Iforiginis not present, abort and ask the user which remote to use.
Method
Step 1 — Capture state and validate preconditions
Run these checks in parallel:
git rev-parse --abbrev-ref HEAD # current branch name
git status --porcelain # must be empty (clean working tree)
git remote # must contain 'origin'Abort with a clear message if:
- Current branch is
main(nothing to clean up). git status --porcelainis non-empty (uncommitted changes).originremote does not exist.
Save the current branch name as DEV_BRANCH for later steps.
Step 2 — Fetch latest refs and verify merge status
git fetch origin --pruneThen check whether every commit on DEV_BRANCH is reachable from origin/main:
git merge-base --is-ancestor <DEV_BRANCH> origin/main- Exit code
0→ branch is fully merged. Proceed to Step 3. - Exit code
1→ branch has commits not inorigin/main. STOP and report to the user:- Show the unmerged commits:
git log --oneline origin/main..<DEV_BRANCH> - Tell the user the branch is not merged and the skill will not delete it.
- Do not continue to subsequent steps.
- Show the unmerged commits:
Step 3 — Switch to main and pull
git checkout main
git pull origin main --ff-onlyUse --ff-only so the pull aborts cleanly if something unexpected happened upstream rather than creating a merge commit silently.
Step 4 — Delete the local dev branch
git branch -d <DEV_BRANCH>Use lowercase -d (safe delete). It refuses to delete if not merged — which should not happen since Step 2 already verified the merge, but the double-check is intentional. Do not fall back to -D.
Step 5 — Delete the remote dev branch if it still exists
First check whether the remote branch is still present (the maintainer may have already deleted it after merging the PR):
git ls-remote --heads origin <DEV_BRANCH>- Output empty → remote already deleted. Skip the delete and report "remote branch already removed".
- Output non-empty → delete it:
git push origin --delete <DEV_BRANCH>If the push fails (permission denied, protected branch, etc.), report the error to the user — do not retry with force.
Step 6 — Report final state
Summarize what changed in a short message:
- Current branch (should be
main) and its short SHA. - Whether the local dev branch was deleted.
- Whether the remote dev branch was deleted or was already gone.
Example Walk-through
User finishes work on dev-14156 which has been merged into main via PR:
Step 1: HEAD=dev-14156, working tree clean, origin present. ✓
Step 2: git fetch origin --prune
git merge-base --is-ancestor dev-14156 origin/main → 0 ✓ merged
Step 3: git checkout main
git pull origin main --ff-only → main now at <sha>
Step 4: git branch -d dev-14156 → deleted
Step 5: git ls-remote --heads origin dev-14156 → non-empty
git push origin --delete dev-14156 → deleted
Step 6: Report: on main @ <sha>; local dev-14156 deleted; remote dev-14156 deleted.Notes
- The skill is a pure git workflow — no IDA Pro MCP or codebase analysis is involved.
- If the user wants to clean up a different branch than the one currently checked out, they should switch to it first; this skill only operates on
HEAD. - The skill never force-deletes (
-D) or force-pushes. If a step refuses, that is a signal to stop and surface the situation, not to override.
Arquivos desta versão
agents/143 B
- openai.yaml43 B
- SKILL.md4.9 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Não | Não |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaPrompt injection · injection.no_confirmationSKILL.md:71
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-dcf2020 | 13 de nov. de 2026 | dcf2020 | 13320dfc | Assinada | – |
Mais de HLND2T
Tudo deste publicadorMais em Relatórios e compliance
Ver a categoria- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login