git-snapshot-rollback
存档当前的失败尝试分支，并安全回退到特定历史提交
Works with
---
name: git-snapshot-rollback
description: 存档当前的失败尝试分支，并安全回退到特定历史提交
license: Apache-2.0
---
# Git Snapshot & Rollback
此技能通过自动化脚本确保在回退 Git 提交时，不仅保留了当前的尝试（Snapshot），还通过 `ARCHIVE.md` 构建了一个可追溯的决策链表。
## 核心工作流
### 1. 确认回退目标
- 获取用户想要回退到的目标 Commit Hash。
- 询问或总结回退的具体原因（Reason）。
### 2. 执行自动化回退脚本
- **在执行前，必须询问用户是否需要将存档分支推送到远端仓库。**
- 使用 `run_shell_command` 调用技能内置脚本：
- 如果用户同意推送：`python3 <path_to_skill>/scripts/rollback.py <Target_Commit> "<Reason>" --push`
- 如果用户不同意推送（默认）：`python3 <path_to_skill>/scripts/rollback.py <Target_Commit> "<Reason>"`
- **脚本将自动完成**：
1. Commit 当前所有未提交的变更。
2. 创建 `archive/{current_branch}/YYYY-MM-DD-HH-mm` 分支。
3. 更新存档分支的 `ARCHIVE.md` 记录。
4. (可选) 将存档分支推送到远端。
5. 回到原分支并执行 `git reset --hard`。
6. 在原分支更新 `ARCHIVE.md` 并提交回退记录。
7. 列出当前所有领先于远程（未推送）的分支。
### 3. 结果验证
- 检查 `ARCHIVE.md` 是否已正确记录了本次回退的双向链接。
- 确认当前分支已处于目标 Commit 状态。
## 记录规范
- 关于 `ARCHIVE.md` 的具体格式，请参考 [references/log-format.md](references/log-format.md)。
- 每次回退的 Commit Message 必须包含来源存档分支的信息。
## 使用禁令
- 严禁在没有使用此技能的情况下直接执行 `git reset --hard` 来放弃大量工作。
- 不得修改或删除 `ARCHIVE.md` 中的历史记录。More Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).
