chore: prepare release v0.2.1

[sjnims]

Summary

Prepare release v0.2.1 with security hardening, bug fixes, and documentation improvements.

Changes

Security

• Harden validation scripts against bypass attacks (fix: harden example hook validation scripts against bypass attacks #164)
• Prevent command injection in test-hook.sh (fix(security): prevent command injection in test-hook.sh #148)
• Use jq for safe JSON output in example hooks (fix(security): use jq for safe JSON output in example hooks #149)
• Document security scope and trust model (docs: document security scope and trust model for workflow commands #165)

Fixed

• Remove deprecated mode parameter from claude-pr-review workflow (fix: remove deprecated mode parameter from claude-pr-review workflow #171)
• Resolve shellcheck SC1087 errors in validate-hook-schema.sh (fix: resolve shellcheck SC1087 errors in validate-hook-schema.sh #168)
• Replace unofficial cc alias with official claude CLI command
• Issue/PR template improvements and labels configuration fixes

Documentation

• Comprehensive documentation improvements across README, CLAUDE.md, and skills
• Added prerequisites section, shellcheck guidance, secure mktemp patterns

Dependencies

• Updated anthropics/claude-code-action and EndBug/label-sync
• Updated GitHub Actions to latest versions

Checklist

• Version updated in plugin.json (0.2.1)
• Version updated in marketplace.json (metadata.version AND plugins[0].version)
• Version updated in CLAUDE.md
• CHANGELOG.md updated with release notes
• Markdownlint passes
• Version consistency verified

🤖 Generated with Claude Code

[claude]

Claude finished @sjnims's task in 1m 15s —— View job

---

PR Review: Release v0.2.1

Summary

✅ Looks good - This is a well-executed release preparation PR. All version files are synchronized, the changelog is comprehensive and properly formatted, and markdown linting passes cleanly.

What's Good

Version Management

• ✅ Version 0.2.1 is correctly synchronized across all three required files:
  • plugins/plugin-dev/.claude-plugin/plugin.json
  • .claude-plugin/marketplace.json (both metadata.version AND plugins[0].version)
  • CLAUDE.md (Quick Reference section)

Changelog Quality

• ✅ Follows Keep a Changelog format precisely
• ✅ Well-organized sections: Security, Fixed, Changed, Documentation, Dependencies
• ✅ Includes PR references for traceability (e.g., fix: harden example hook validation scripts against bypass attacks #164, fix(security): prevent command injection in test-hook.sh #148, fix(security): use jq for safe JSON output in example hooks #149, docs: document security scope and trust model for workflow commands #165)
• ✅ Comparison links properly updated at the bottom
• ✅ Release date included: 2025-12-13

Markdown Linting

• ✅ All changed markdown files pass markdownlint with no errors
• ✅ Follows repository standards (ATX headers, dash lists, fenced code blocks)

Process Adherence

• ✅ Follows the Version Release Procedure from CLAUDE.md exactly
• ✅ Uses proper release branch naming: release/v0.2.1
• ✅ Commit message follows convention: chore: prepare release v0.2.1
• ✅ PR checklist items all marked complete

Release Content

• ✅ Security-focused release with hardening improvements
• ✅ Bug fixes for workflow issues and shellcheck errors
• ✅ Documentation improvements across the board
• ✅ Dependency updates included

Checklist Verification

All items from the PR checklist are verified:

• Version updated in plugin.json (0.2.1) ✅
• Version updated in marketplace.json (metadata.version AND plugins[0].version) ✅
• Version updated in CLAUDE.md ✅
• CHANGELOG.md updated with release notes ✅
• Markdownlint passes ✅
• Version consistency verified ✅

Ready to Merge

This PR is ready to merge. After merging, don't forget to create the GitHub release using:

gh release create v0.2.1 \
  --target main \
  --title "v0.2.1" \
  --notes "Security hardening, bug fixes, and documentation improvements"

[claude]

❌ CI Failure Analysis: Check Links

Run: #20196631079
Commit: 0c15f5d

Summary

The lychee link checker found 2 broken links in CHANGELOG.md that reference the v0.2.1 tag, which doesn't exist yet because this is the release PR.

Failures Found

File	Line	Issue
CHANGELOG.md	170	https://github.com/sjnims/plugin-dev/compare/v0.2.0...v0.2.1 returns 404
CHANGELOG.md	169	https://github.com/sjnims/plugin-dev/compare/v0.2.1...HEAD returns 404

Expected Behavior

This is expected for release PRs. These comparison links will work correctly once:

1. The PR is merged to main
2. The v0.2.1 tag is created via gh release create v0.2.1

The tag creation makes these GitHub comparison URLs valid.

Resolution

✅ No action needed - This link check failure is expected for release PRs and will resolve automatically after the release tag is created.

According to CLAUDE.md#version-release-procedure, the next steps after merging this PR are:

# After PR is merged
gh release create v0.2.1 \
  --target main \
  --title "v0.2.1" \
  --notes-file - <<'EOF'
[Release notes here]
EOF

Once the tag is created, these comparison URLs will automatically become valid.

---

🤖 Analyzed by Claude