Files
claude-cookbooks/.claude/commands/link-review.md
Jiri De Jonghe f26aa5891c Add Claude Code SDK tutorials and examples (#195)
* Add Claude Code SDK tutorials and examples

This PR adds comprehensive tutorials and examples for the Claude Code SDK, including:
- Research agent implementation with web search capabilities
- Chief of Staff agent with multi-agent coordination
- Observability agent with Docker configuration
- Supporting utilities and documentation

The examples demonstrate key SDK features:
- Multi-turn conversations with ClaudeSDKClient
- Custom output styles and slash commands
- Hooks for automated actions and governance
- Script execution via Bash tool
- Multi-agent orchestration patterns

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: rodrigo olivares <rodrigoolivares@anthropic.com>
Co-authored-by: Alex Notov <zh@anthropic.com>
2025-09-12 15:04:34 -07:00

31 lines
1.3 KiB
Markdown

---
allowed-tools: Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*)
description: Review links in changed files for quality and security issues
---
Review the links in the changed files and check for potential issues:
## Link Quality Checks
1. **Broken Links**: Identify any links that might be broken or malformed
2. **Outdated Links**: Check for links to deprecated resources or old documentation
3. **Security**: Ensure no links to suspicious or potentially harmful sites
4. **Best Practices**:
- Links should use HTTPS where possible
- Internal links should use relative paths
- External links should be to stable, reputable sources
## Specific Checks for Anthropic Content
- Links to Claude documentation should point to the latest versions
- API documentation links should be current
- Model documentation should reference current models, not deprecated ones
- GitHub links should use the correct repository paths
## Report Format
Provide a clear summary with:
- ✅ Valid and well-formed links
- ⚠️ Links that might need attention (e.g., HTTP instead of HTTPS)
- ❌ Broken or problematic links that must be fixed
If all links look good, provide a brief confirmation.
**IMPORTANT: Post your review as a comment on the pull request using the command: `gh pr comment $PR_NUMBER --body "your review content"`**