git
Manage Git History, Conflicts, and Recovery
Unclear commits, conflicting branches, and lost changes can slow repository work. This skill guides focused commits, history inspection, conflict resolution, and recovery using established Git practices.
使用我的智慧代理安裝
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "git" from https://skillstore.io/skills/shreyam1008-git.md and its manifest at https://skillstore.io/api/skills/shreyam1008-git/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
測試它
正在使用「git」。 I changed login behavior and corrected documentation. How should I organize the commits?
預期結果:
- Separate the login change from the documentation correction.
- Stage each logical change selectively and verify the staged diff.
- Use a feature commit for login behavior and a documentation commit for the correction.
- Run relevant tests before committing the behavior change.
正在使用「git」。 A bad commit is already on a shared branch. What is the appropriate undo strategy?
預期結果:
- Prefer a revert that adds an inverse commit and preserves shared history.
- Inspect later changes for dependencies and check for conflicts.
- Validate the resulting behavior before publishing the revert.
- Avoid resetting or force-pushing the shared branch.
正在使用「git」。 I cannot find a commit after moving my branch. How should I investigate?
預期結果:
- Inspect the reflog for the previous branch position.
- Confirm that the candidate commit contains the expected changes.
- Protect current work before choosing a recovery operation.
- Recovery may fail if the required Git objects are no longer retained.
安全審計
安全All 27 static findings are false positives: Markdown formatting and ordinary Git guidance were mistaken for shell execution or system reconnaissance. Destructive operations are identified with warnings, and shared-history safeguards are explicit. No evidence found of prompt injection, credential exfiltration, or malicious execution.
風險因素
⚙️ 外部命令 (25)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/shreyam1008-git/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/shreyam1008-git?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/shreyam1008-git?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/shreyam1008-git/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/shreyam1008-git.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 引用
shreyam1008. (2026). git security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-git/audits/1BibTeX 引用
@techreport{shreyam1008-shreyam1008-git-2026,
author = {shreyam1008},
title = {git security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/shreyam1008-git/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: "git security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "shreyam1008"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/shreyam1008-git/audits/1"
identifiers:
- type: other
value: "skillstore:shreyam1008-git:audit:1"
description: "Skillstore immutable audit report identifier"
比較變體
3 個可安裝變體每位作者的技能都保留為獨立的可安裝項目。推薦變體依 Skillstore 證據排序。
為何此變體排名第一
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Prepare focused commits
Separate unrelated changes and draft consistent commit messages before opening a pull request.
Coordinate branch integration
Choose merge or rebase strategies while preserving shared history and validating conflict resolutions.
Investigate regressions and recovery
Trace changes with history tools, plan bisect checks, and identify recovery options for misplaced commits.
試試這些提示
Inspect my repository status and diffs. Summarize staged and unstaged changes without modifying files or history.
Review my changes and propose separate logical commits with Conventional Commits messages. Wait for approval before staging or committing.
Inspect conflicts between [feature branch] and [target branch]. Propose resolutions that preserve intended behavior and identify tests before continuing integration.
Inspect status, log, and reflog to locate [lost change]. Explain recovery options and risks; request approval before any reset or history rewrite.
最佳實務
- Inspect status and diffs, then obtain explicit approval before discarding changes or rewriting history.
- Keep commits focused and validate behavior with builds and tests after resolving conflicts.
- Preserve shared history and follow repository review, branch protection, and deployment policies.
避免
- Using hard reset or file restore without checking and protecting uncommitted work.
- Rebasing or force-pushing branches that other contributors depend on.
- Accepting every conflict from one side without reviewing intended behavior or running tests.
常見問題
Which assistants are supported?
Does the skill include executable scripts?
Does it require a paid service?
Should I rebase a shared branch?
Can it recover every lost change?
How does it reduce accidental secret exposure?
開發者詳細資訊
作者
shreyam1008授權
MIT
Skillstore 修訂
r1
版本提示
作者未聲明版本。
儲存庫
https://github.com/shreyam1008/shre-skills/tree/ba9787f41c2fe1be1062eeb6322bc339a1026383/skills/git引用
bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5
維護新鮮度
2026/10/2
使用量
0 次下載 · 0 次瀏覽
檔案結構
📄 SKILL.md