smithery.ai

review-readme

檢查 README.md 是否需要根據最近的 commits 更新。Use when the user wants to review whether README.md is up-to-date with recent code changes.

First seen Mar 21, 2026

Installation

$ npx skills add https://smithery.ai

Summary

  • 檢查 README.md 是否需要根據最近的 commits 更新。Use when the user wants to review whether README.md is up-to-date with recent code changes.
  • Triggers on requests like "review readme", "check readme", "檢查 README", "更新 README", or when the user invokes /review-readme.
  • Analyzes all commits since the last README.md modification and suggests specific updates if needed.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,827 B
  • docs SUMMARY.md 408 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Review README

Analyze commits since the last README.md modification and determine whether README.md needs updating.

Workflow

  1. Find the last README.md commit

``bash git log -1 --format="%H %s" -- README.md ``

  1. List all commits since that point

``bash git log <last-readme-commit>..HEAD --oneline --no-merges `` If no commits exist, report "README.md is up-to-date" and stop.

  1. Analyze each commit for README-relevance

Review diffs (git show <hash> --stat and git show <hash> as needed). Flag changes that affect README.md: - New or removed features / generation modes - New or changed commands (npm run ...) - New dependencies or prerequisites - Architecture changes (new composables, stores, workers, routes) - Changed API / configuration patterns - New environment variables or setup steps

  1. Report findings in zh-TW

Present a structured summary: - 相關 commits: Commits that may require README updates, with brief reason - 建議修改: For each, describe the specific README section(s) to update and the proposed change - 無需修改: Commits confirmed irrelevant (bug fixes, style tweaks, test-only, etc.)

  1. Confirm and apply

Ask the user to confirm the proposed changes before editing README.md. After confirmation, apply edits and show a summary of what was changed.