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.
๋ด ์์ด์ ํธ๋ก ์ค์น
์ด ์์ฒญ์ ์์ด์ ํธ์ ๋ณต์ฌํ์ธ์. ๊ณต์ Skill ํ์ด์ง์ ๋งค๋ํ์คํธ๊ฐ ํฌํจ๋์ด ์์ต๋๋ค.
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.์์ด์ ํธ๋ ๊ณ์ํด์ ๊ณํ์ ํ์ํ๊ณ ๋ณด์ ์ ์ฑ ์์ ์๊ตฌํ๋ ํ์ธ์ ์์ฒญํด์ผ ํฉ๋๋ค.
์์ด์ ํธ๊ฐ ์ฝ๊ธฐ ์ฌ์ด ๋ฆฌ์์ค
AI ์์ด์ ํธ, ํฌ๋กค๋ฌ, ์คํฌ๋ฆฝํธ๊ฐ ์ ์ฒด ํ์ด์ง ๋์ ์ ๋ฆฌ๋ ์ปจํ ์คํธ๋ง ํ์ํ ๋ ์ด ๋งํฌ๋ฅผ ์ฌ์ฉํ์ธ์.
ํ ์คํธํด ๋ณด๊ธฐ
"w-git-repair" ์ฌ์ฉ ์ค์ ๋๋ค. My branch is behind the remote and Git reports conflicts. What should I do?
์์ ๊ฒฐ๊ณผ:
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.
"w-git-repair" ์ฌ์ฉ ์ค์ ๋๋ค. I checked out a commit and now I am in detached HEAD. Help me recover.
์์ ๊ฒฐ๊ณผ:
- 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.
๋ณด์ ๊ฐ์ฌ
์์ All 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.
์ํ ์์ธ
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (2)
์ด ๋ณด๊ณ ์ ๊ณต์ ๋ฐ ์ธ์ฉ
๋ฒ์ ์ด ์ง์ ๋ ํ๊ฐ ๋ณด๊ณ ์, ์ค๋ฆฝ ๋ฐฐ์ง, ์๋ฒ ๋ ์นด๋ ๋ฐ ์ธ์ฉ์ ๊ณต์ ํ์ธ์. Skillstore๋ ๊ทผ๊ฑฐ๋ฅผ ๋ณด๊ณ ํ์ง๋ง ์ด Skill์ ์์ ์ฌ๋ถ๋ฅผ ํ๋จํ์ง ์์ต๋๋ค.
๋ณด๊ณ ์ ๋งํฌ ๋ณต์ฌ
https://skillstore.io/skills/blockmatic-w-git-repair/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown ๋ฐฐ์ง
[](https://skillstore.io/skills/blockmatic-w-git-repair?utm_source=security_passport_badge)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>์๋ฒ ๋ ์นด๋
<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>ํ์ ์ธ์ฉ (APA ยท BibTeX ยท CFF)
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/1BibTeX ์ธ์ฉ
@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"
Skillstore ์ ์
์ด ์ ์์ ์ด์ ์ฆ๊ฑฐ ์ ๋ขฐ๋: ์ค๊ฐ๋ง๋ค ์ ์๋ ๊ฒ
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.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
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.
๋ชจ๋ฒ ์ฌ๋ก
- 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.
ํผํ๊ธฐ
- 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.
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
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?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
blockmatic๋ผ์ด์ ์ค
MIT
Skillstore ๋ฆฌ๋น์
r1
๋ฒ์ ์๋ด
์์ฑ์๊ฐ ๋ฒ์ ์ ์ ์ธํ์ง ์์์ต๋๋ค.
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/blockmatic/basilic-skills/tree/5fa16493413923e31f1df31f7260224f0f291d9e/skills/w-git-repair์ฐธ์กฐ
71c22685fcd4644d03ae28812e97ea1562ebe3fe
์ ์ง๋ณด์ ์ต์ ์ฑ
2026. 9. 20.
์ฌ์ฉ๋
0 ๋ค์ด๋ก๋ ยท 0 ์กฐํ
ํ์ผ ๊ตฌ์กฐ