w-git-repair
Repair Git Problems With Safe Commands
Git conflicts, detached HEAD states, and upstream divergence can cause accidental data loss. This skill inspects repository state and proposes the smallest repair commands with confirmation for destructive actions.
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 "w-git-repair" from https://skillstore.io/skills/blockmatic-w-git-repair.md and its manifest at https://skillstore.io/api/skills/blockmatic-w-git-repair/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.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 "w-git-repair". My branch is behind the remote and Git reports conflicts. What should I do?
Resultado esperado:
The branch has diverged. I will first inspect status, tracking information, and recent history, then propose the smallest integration steps. I will wait for confirmation before changing files.
Usando "w-git-repair". I checked out a commit and now I am in detached HEAD. Help me recover.
Resultado esperado:
- Confirm whether the detached commit contains work that must be preserved.
- Identify an existing branch or create a new branch only after reviewing the current state.
- Recheck status after the authorized action and verify that the work is reachable.
Auditoría de seguridad
SeguroAll three static signals are false positives. The environment-file signal describes rules that prevent committing secrets, while the two command signals identify inline Git examples in Markdown rather than executable shell code. No additional semantic security findings were identified.
Factores de riesgo
⚙️ Comandos externos (2)
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/blockmatic-w-git-repair/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/blockmatic-w-git-repair?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/blockmatic-w-git-repair?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/blockmatic-w-git-repair/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/blockmatic-w-git-repair.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
blockmatic. (2026). w-git-repair security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/blockmatic-w-git-repair/audits/1Cita BibTeX
@techreport{blockmatic-blockmatic-w-git-repair-2026,
author = {blockmatic},
title = {w-git-repair security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/blockmatic-w-git-repair/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: "w-git-repair security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "blockmatic"
date-released: "2026-09-20"
url: "https://skillstore.io/skills/blockmatic-w-git-repair/audits/1"
identifiers:
- type: other
value: "skillstore:blockmatic-w-git-repair: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
Recover a Detached HEAD
Inspect the current commit and branches, then receive a cautious path back to a working branch.
Resolve Upstream Divergence
Compare local and remote tracking information and choose a minimal integration approach.
Handle Local Conflicts
Review conflict status and receive explained next steps that preserve unrelated work.
Prueba estos prompts
Inspect my current Git status, branch tracking, and recent relevant history. Summarize the problem and do not change files.
Review the repository state and propose the smallest safe steps to resolve the current conflict. Explain what each step changes.
Determine whether an interrupted merge or rebase is in progress. List the safe recovery choices, and ask for confirmation before any destructive command.
Analyze local and upstream divergence, preserve unrelated work, and recommend an integration strategy. Treat history rewriting as unavailable unless I explicitly request it.
Mejores prácticas
- Provide the exact repository state and the goal before requesting a repair.
- Review each proposed command and confirm actions that can discard work.
- Preserve unrelated staged, unstaged, and untracked changes.
Evitar
- Do not approve destructive commands without reviewing their effect.
- Do not rewrite published history to solve an unexamined conflict.
- Do not force-push or bypass hooks as a shortcut.
Preguntas frecuentes
Does this skill run Git commands automatically?
Can it repair merge conflicts?
Can it recover a detached HEAD?
Does it support upstream divergence?
Will it use hard reset or clean automatically?
Can it rewrite published history?
Detalles del desarrollador
Autor
blockmaticLicencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Ref.
71c22685fcd4644d03ae28812e97ea1562ebe3fe
Actualidad del mantenimiento
20/9/2026
Uso
0 descargas · 0 vistas
Estructura de archivos