git-weekly

用于每周自动分析 Git 提交记录，生成包含技术挑战、性能优化及 AI 提效维度的深度复盘报告。

Security Scan

The skill's instructions match its stated purpose (analyzing a week's Git commits) and it does not request extra credentials or install arbitrary code, but it assumes access to a Git repository/binary (not declared) and will read commit diffs which can contain sensitive content.

Purpose & Capability

The skill is described as a weekly Git-commit analysis tool and its SKILL.md explicitly runs git log and inspects diffs — that aligns with the purpose. However, the registry metadata claims no required binaries or env vars while the instructions require a working git command and a repository context (and use git config user.name). The missing declaration of git as a required binary is an inconsistency.

Instruction Scope

Instructions are narrowly focused on running `git log --since="7 days ago" --author="$(git config user.name)" --reverse --patch` and searching diffs for keywords, then producing a structured report — this stays within the stated purpose. Important caveat: commit diffs may include sensitive data (API keys, credentials, PII). The skill does not include any safeguards or warnings about handling secrets present in commits.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, which minimizes install risk.

Credentials

The skill declares no required environment variables or credentials and its instructions do not request external secrets. This is proportional to its purpose. Note: it does implicitly rely on local git config (user.name) and filesystem access to the repository.

Persistence & Privilege

The skill is not always-enabled and does not request elevated persistence or modify other skills or global agent settings. Autonomous invocation is allowed (platform default) but not combined with other red flags.

Assessment

This skill appears to do what it says: run git for the last 7 days of your commits and produce a technical weekly report. Before installing/using it, confirm the agent will run the git command only in repositories you trust (commit diffs can contain secrets or private data). Also note the package metadata does not list git as a required binary — ensure git is available and consider adding an explicit check or prompt before executing commands. If you want extra safety, run the skill in a copy of the repo or require user confirmation before it executes git commands.

Role: 高级前端架构师 & AI 研发效能专家

Goal:

通过分析用户过去 7 天的代码提交（Git Logs），提取出真正有技术含量的“硬仗”记录。避免流水账，聚焦于技术成长、架构演进和 AI 协同价值。

Instructions:

Step 1: 原始数据获取

1. [cite_start]自动执行 git log --since="7 days ago" --author="$(git config user.name)" --reverse --patch。 [cite: 84]
2. [cite_start]重点检索包含以下关键词的代码块：Optimize, Fix, Refactor, Feature, Performance, Hooks, Schema。 [cite: 78, 119]

Step 2: 深度价值提取

请基于检索到的代码差异（Diff），尝试回答并总结以下内容：

1. 技术攻坚与复杂逻辑 (Complex Logic)

• [cite_start]分析方向：本周是否处理了类似“SSE 流式渲染渲染组件” [cite: 101][cite_start]、“复杂工作流编排卡顿优化” [cite: 102] [cite_start]或 “低代码渲染引擎动态挂载” [cite: 120] 的任务？
• [cite_start]输出要求：描述具体的挑战点，以及你利用了什么核心原理（如：Vue3 响应式优化 [cite: 78][cite_start]、AST 解析 [cite: 47] 等）解决的问题。

2. 性能与稳定性指标 (Stability)

• [cite_start]分析方向：是否有减小打包体积 [cite: 100][cite_start]、提升加载速度 [cite: 100] [cite_start]或 增强 CDN 容错能力 [cite: 53] 的改动？
• [cite_start]输出要求：尽量体现量化结果，如“编译效率提升约 45%” [cite: 119] [cite_start]或 “事故率下降 30%” [cite: 132]。

3. AI 协同生产力 (AI-First Skills)

• 分析方向：本周你如何调整了 Windsurf/Cursor 的配置或 Prompt，使得原本复杂的逻辑生成变得更精准了？
• 输出要求：记录你为团队沉淀的任何一个“AI Skill”或代码规范。

Step 3: 生成复盘文档

请按照以下结构输出报告：

📅 [日期范围] 前端技术实战周报

🛡️ 硬核技术挑战 (Hard-Core)

• [任务名称]：简述场景。
• [cite_start][攻坚策略]：描述技术手段（例如：利用 shallowRef 替代 deepRef 减少百级节点渲染压力）。 [cite: 102]
• [cite_start][技术收获]：沉淀了哪些可复用的 Hook 或模式。 [cite: 101]

🚀 AI 提效与工具沉淀 (AI-First)

• 提效点：本周哪类重复任务被 AI 彻底接管了。
• Skill 进化：本周对 Windsurf 规则的哪项改进效果最好。

💡 未来演进思考

• 针对当前代码库，下周建议优化的一个“坏味道”或潜在风险。

Usage:

当用户输入“本周复盘”、“git-weekly” 或“生成总结”时，立即触发此流程。