[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TYYGXR72P63ENF7Z435JH":3,"skill-same:01M79TYYGXR72P63ENF7Z435JH":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79TYYGXR72P63ENF7Z435JH","py-changelog",null,"Maintain the release-history.rst changelog for a Python project before publishing a new version. Use when the user wants to prepare release notes, update changelog, or is about to publish\u002Ftag a new version.","MacHu-GWU\u002Fchinese_to_english_punctuation-project","MacHu-GWU","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6800411?v=4","01M79BMG0V767YAMAMTG1ZQ7FY","Sanhe Hu","01M79TYW4P2VAKSVBQ5E13PYN9",0,"MIT","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fchinese_to_english_punctuation-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpy-changelog\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: py-changelog\ndescription: Maintain the release-history.rst changelog for a Python project before publishing a new version. Use when the user wants to prepare release notes, update changelog, or is about to publish\u002Ftag a new version.\n---\n\nYou are maintaining `release-history.rst` for a Python project. Your job is to keep the target version's section accurate and complete based on git history. You never touch the `x.y.z (Backlog)` section.\n\n## Step 1: Gather State\n\nRun these commands to understand the current state:\n\n```bash\n# Last published tag\ngit describe --tags --abbrev=0\n\n# pyproject.toml version (this is the target version to release)\ngrep '^version' pyproject.toml\n```\n\n**Determine target version:**\n- `pyproject.toml version` is always the source of truth for the new release target.\n- `last tag` is the baseline for git history comparison.\n\n## Step 2: Pull Git Changes (Feed to AI)\n\nUse `{LAST_TAG}` = the tag from Step 1.\n\n```bash\n# Commit intent summary\ngit log {LAST_TAG}..HEAD --oneline\n\n# Files changed (concise overview)\ngit diff {LAST_TAG}..HEAD --stat\n\n# Actual Python code changes (for understanding what really changed)\ngit diff {LAST_TAG}..HEAD -- '*.py'\n```\n\nRead these outputs carefully. They are the ground truth for what changed.\n\n## Step 3: Read release-history.rst Format\n\nRead the first 100 lines of `release-history.rst`:\n\n```bash\nhead -100 release-history.rst\n```\n\nThis shows you:\n- The RST formatting conventions used in this project\n- The section categories (Features and Improvements, Minor Improvements, Bugfixes, Breaking Changes, Miscellaneous)\n- The `x.y.z (Backlog)` placeholder at the top — **never modify this section**\n- The Backlog content — use it as **reference only** to understand what the user plans, do not copy or move it\n\n## Step 4: Determine Action\n\n**Case A — Target version section already exists in release-history.rst:**\n\nCompare the existing content against what git history reveals:\n- Is anything missing that git history shows?\n- Is anything written that git history does not support?\n- Are the descriptions accurate and clear?\n\nUpdate the section in-place to be complete and accurate. Do not leave gaps.\n\n**Case B — Target version section does not exist:**\n\nInsert a new section immediately after the `x.y.z (Backlog)` block (after its blank line), following this exact RST format:\n\n```rst\n{VERSION} ({DATE})\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n**Features and Improvements**\n\n- ...\n\n**Minor Improvements**\n\n- ...\n\n**Bugfixes**\n\n- ...\n\n**Miscellaneous**\n\n- ...\n```\n\nUse today's date. Omit any category that has no entries (do not leave empty `**Category**` headers with no bullets).\n\n## Step 5: Write Directly\n\nEdit `release-history.rst` directly. No need to ask the user for confirmation — the file is git-tracked and can be reverted.\n\n## Rules\n\n- **Never touch `x.y.z (Backlog)`** — not its header, not its content, not its blank lines.\n- Backlog content is reference only. Do not copy bullet points verbatim from Backlog into the version section.\n- Base all changelog entries on what git history actually shows, not assumptions.\n- Keep descriptions user-facing and concise (what changed and why it matters, not implementation details).\n- Follow the RST formatting exactly as seen in existing entries.\n- If a category has no entries, omit the entire category header.\n","You are maintaining `release-history.rst` for a Python project. Your job is to keep the target version's section accurate and complete based on git history. You never touch the `x.y.z (Backlog)` section.\n\n## Step 1: Gather State\n\nRun these commands to understand the current state:\n\n```bash\n# Last published tag\ngit describe --tags --abbrev=0\n\n# pyproject.toml version (this is the target version to release)\ngrep '^version' pyproject.toml\n```\n\n**Determine target version:**\n- `pyproject.toml version` is always the source of truth for the new release target.\n- `last tag` is the baseline for git history comparison.\n\n## Step 2: Pull Git Changes (Feed to AI)\n\nUse `{LAST_TAG}` = the tag from Step 1.\n\n```bash\n# Commit intent summary\ngit log {LAST_TAG}..HEAD --oneline\n\n# Files changed (concise overview)\ngit diff {LAST_TAG}..HEAD --stat\n\n# Actual Python code changes (for understanding what really changed)\ngit diff {LAST_TAG}..HEAD -- '*.py'\n```\n\nRead these outputs carefully. They are the ground truth for what changed.\n\n## Step 3: Read release-history.rst Format\n\nRead the first 100 lines of `release-history.rst`:\n\n```bash\nhead -100 release-history.rst\n```\n\nThis shows you:\n- The RST formatting conventions used in this project\n- The section categories (Features and Improvements, Minor Improvements, Bugfixes, Breaking Changes, Miscellaneous)\n- The `x.y.z (Backlog)` placeholder at the top — **never modify this section**\n- The Backlog content — use it as **reference only** to understand what the user plans, do not copy or move it\n\n## Step 4: Determine Action\n\n**Case A — Target version section already exists in release-history.rst:**\n\nCompare the existing content against what git history reveals:\n- Is anything missing that git history shows?\n- Is anything written that git history does not support?\n- Are the descriptions accurate and clear?\n\nUpdate the section in-place to be complete and accurate. Do not leave gaps.\n\n**Case B — Target version section does not exist:**\n\nInsert a new section immediately after the `x.y.z (Backlog)` block (after its blank line), following this exact RST format:\n\n```rst\n{VERSION} ({DATE})\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n**Features and Improvements**\n\n- ...\n\n**Minor Improvements**\n\n- ...\n\n**Bugfixes**\n\n- ...\n\n**Miscellaneous**\n\n- ...\n```\n\nUse today's date. Omit any category that has no entries (do not leave empty `**Category**` headers with no bullets).\n\n## Step 5: Write Directly\n\nEdit `release-history.rst` directly. No need to ask the user for confirmation — the file is git-tracked and can be reverted.\n\n## Rules\n\n- **Never touch `x.y.z (Backlog)`** — not its header, not its content, not its blank lines.\n- Backlog content is reference only. Do not copy bullet points verbatim from Backlog into the version section.\n- Base all changelog entries on what git history actually shows, not assumptions.\n- Keep descriptions user-facing and concise (what changed and why it matters, not implementation details).\n- Follow the RST formatting exactly as seen in existing entries.\n- If a category has no entries, omit the entire category header.\n",{"name":5,"description":7},"main","79d918ea9cbf621ab51c07946488f54bfc352fca",".claude\u002Fskills\u002Fpy-changelog","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fchinese_to_english_punctuation-project","https:\u002F\u002Fchinese-to-english-punctuation.readthedocs.io\u002F","https:\u002F\u002Fgithub.com\u002FMacHu-GWU","Founder mindset, engineer’s hands. Customers first, product second. Forward-deployed AI architect · ex-AWS · 200+ OSS libs · 4K+ commits\u002Fyr","2026-11-07 07:29:35",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MacHu-GWU\u002Fchinese_to_english_punctuation-project --skill py-changelog",{"tool":38,"command":39},"bunx","bunx skills add MacHu-GWU\u002Fchinese_to_english_punctuation-project --skill py-changelog",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MacHu-GWU\u002Fchinese_to_english_punctuation-project --skill py-changelog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fchinese_to_english_punctuation-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpy-changelog\u002FSKILL.md",true,[],[47,54,61],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M79TZAMSR3M8M5T2CGNHRE42","write-pypi-skill","A meta skill that reads the Python library at the current working directory and generates a reusable Agent Skill for it, named after the package, that documents the library's public API and, if present, its command line interface. The user invokes this when they want to turn a local Python library into a Claude skill so future sessions can use the library through its public surface without re-reading the source.","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fchinese_to_english_punctuation-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-pypi-skill\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TZ81RDDZEY2Z82P5AATCQ","write-agent-skill","Claude Code Agent Skill Author Guide","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fchinese_to_english_punctuation-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-agent-skill\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TZ11NXFGS064WZMS5VN9D","pypi-chinese_to_english_punctuation","Converts Chinese full-width punctuation into English half-width punctuation and fixes the spacing between Chinese characters and adjacent English words or numbers, while preserving leading indentation so Markdown and reStructuredText code blocks stay intact. Covers commas, periods, colons, semicolons, question and exclamation marks, round brackets, square brackets, angle brackets, curly braces, and double quotes. The single public function is process, which takes text and returns text. A command line tool named c2ep exposes the same behavior, with a text subcommand that reads from stdin or an argument and writes to stdout, and a file subcommand that rewrites a UTF-8 file in place. Use this when normalizing punctuation in mixed Chinese and English documents. Generated for chinese_to_english_punctuation version 0.1.2. Higher installed versions should generally be compatible, lower versions may still work but correctness is not guaranteed.","https:\u002F\u002Fgithub.com\u002FMacHu-GWU\u002Fchinese_to_english_punctuation-project\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpypi-chinese_to_english_punctuation\u002FSKILL.md",[],[]]