reusable cspell, claude pr reviews, link issues and prs

[kernelsam]

Issue number: senzing-factory/build-resources#232 senzing-factory/build-resources#227 senzing-factory/build-resources#10

---

Resolves senzing-factory/build-resources#232
Resolves senzing-factory/build-resources#227
Resolves senzing-factory/build-resources#10

[github-actions]

🤖 Claude Code Review

This file contains a PR code review prompt template with a checklist for reviewing pull requests. It includes:

1. Code Quality checklist - style guide compliance, no commented-out code, meaningful variable names, DRY principle, and defect identification

2. Testing checklist - unit tests, integration tests, edge cases, and test coverage requirements (>80%)

3. Documentation checklist - README updates, API docs, inline comments, and CHANGELOG.md updates

4. Security checklist - no hardcoded credentials, input validation, proper error handling, no sensitive data in logs, and a specific flag for license files (.lic) containing strings starting with AQAAAD

5. Pull Request Diff section - Contains an example diff showing:

   • Addition of .github/workflows/claude-pr-review.yaml - a new workflow for Claude PR reviews
   • Addition of .github/workflows/link-issues-to-pr-post-merge.yaml - a workflow to link issues after PR merge
   • Modification of .github/workflows/spellcheck.yaml - refactored to use a reusable workflow from senzing-factory/build-resources

The template asks for ✅/❌ assessment of each checklist item with explanations for any issues found. Would you like me to help you use this template to review a PR, or modify the template itself?

Automated code review analyzing defects and coding standards