跳到正文
cccskills
免费在 GitHub 公开

updates

Summarize user-facing project changes from the last 7 days. Use when the user says "/updates", asks for recent updates, wants a changelog-style summary, or wants the most important feature changes from the past week.

中文简介正在准备中。当前显示原文说明。

jtenniswood/espcontrol星标 1,120(GitHub 1,120 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件(2)

  • SKILL.md2.7 KB
  • agents/openai.yaml274 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

/updates

Summarize what changed in this project over the last 7 days, focusing on user-facing features and behavior rather than implementation details.

Workflow

1. Collect Recent Changes

Use the current date as the endpoint and inspect commits from the last 7 days.

git status --short --branch
git fetch origin --prune
git log --since="7 days ago" --date=short --pretty=format:'%h %ad %s' --decorate
git log --since="7 days ago" --name-only --pretty=format:'commit %h %ad %s' --date=short

If the local branch is behind or stale, note that the summary is based on the available local history unless a fetch succeeded.

2. Understand User Impact

For each meaningful change, inspect enough context to explain what a user can now do, see, configure, or rely on.

Useful commands:

git show --stat <commit>
git show --name-only <commit>
git show -- <path>

Prioritize these as user-facing:

  • New visible UI behavior, controls, screens, or settings
  • Firmware capabilities, device support, setup, update, or reliability changes
  • Documentation that helps users operate, configure, or troubleshoot the project
  • Release, install, or build changes that affect how users receive the project

Usually skip these unless they clearly affect users:

  • Internal refactors
  • Formatting-only changes
  • Test-only changes
  • CI-only maintenance
  • Dependency bumps without a visible change

3. Order by Importance

Sort the summary by practical user impact:

  1. New or expanded capabilities
  2. Fixes for broken or confusing user workflows
  3. Reliability, compatibility, or update improvements
  4. Documentation or setup improvements
  5. Minor polish

When importance is close, put broader changes before narrow device- or page-specific changes.

4. Write the Update

Use one sentence per item in this format:

Feature: description of the user-facing change.

Rules:

  • Keep each item to one sentence.
  • Use approachable, non-developer language.
  • Mention the feature or area first, then the benefit.
  • Avoid commit hashes, file names, and developer terms unless the user asks.
  • Combine related commits into one item when they deliver the same user-facing outcome.
  • If there were no user-facing changes, say that clearly and mention that recent work appears to be internal maintenance.

Output Format

Updates from <start date> to <end date>:

- Feature: <one-sentence description>
- Feature: <one-sentence description>

If the 7-day window is ambiguous, use exact dates in the heading.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Clean up completed Git branches and worktrees for this repository both locally and on GitHub. Use when the user asks to remove complete, completed, merged, stale, finished, or done branches, delete merged GitHub branches, tidy local worktrees, prune completed PR branches, or clean up branches and worktrees after pull requests have merged.

中文简介正在准备中。当前显示原文说明。

jtenniswood/espcontrol11202026年10月26日 更新

Clean up local branch worktree folders for this repository after their branches or pull requests have merged to main. Use when the user asks to remove merged branch folders, tidy local worktrees, clean old feature branch directories, prune merged PR worktrees, or clean up local development folders without impacting main.

中文简介正在准备中。当前显示原文说明。

jtenniswood/espcontrol11202026年10月26日 更新

compile

免费

Test compile ESPHome firmware for all devices using Docker and fix any YAML or configuration errors until every device compiles successfully. Use when the user says "/compile", "test compile", "compile check", "build test", "check builds", "verify compile", or wants to make sure all devices compile before committing.

中文简介正在准备中。当前显示原文说明。

jtenniswood/espcontrol11202026年10月26日 更新

Review EspControl repository changes specifically for missing, stale, excessive, or misplaced documentation. Use when the user asks for a documentation coverage review, asks whether a feature or behavior change is concisely documented, invokes $docs-review, or explicitly wants docs checked as a secondary pass during a pull request, branch, or local diff review.

中文简介正在准备中。当前显示原文说明。

jtenniswood/espcontrol11202026年10月26日 更新

Provide an expert codebase review for this repository. Use when the user says "Expert Review" or "/expert-review", asks for an expert review, wants refactoring or codebase improvement recommendations, wants consistency and quality assessed, or asks how to reduce duplication, improve component use, preserve the end-user experience, and keep upgrades cleanly migratable.

中文简介正在准备中。当前显示原文说明。

jtenniswood/espcontrol11202026年10月26日 更新

Reimagine this repository from first principles using the current product and user experience as the target. Use when the user says "/expert-reset", asks how the project should be rebuilt if starting again, wants bold architecture or component-structure recommendations, or wants a research-only reset plan unconstrained by current implementation details.

中文简介正在准备中。当前显示原文说明。

jtenniswood/espcontrol11202026年10月26日 更新

查看 jtenniswood 的全部技能

报告此技能的问题