## Summary
- Adds a tip to the gitea skill's Tips section documenting that tea CLI uses `--description`/`-d` flag for PR body content, not `--body` like gh CLI
- Helps prevent failed commands when users are used to gh CLI syntax
## Test plan
- [x] Verify the tip is correctly placed in the Tips section of skills/gitea/SKILL.md
Closes #5
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Documents that tea CLI uses --description/-d flag for PR body content,
not --body like the gh CLI. This helps avoid failed commands when
transitioning from gh CLI.
Closes#5🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
LGTM - This PR adds a helpful tip documenting that tea CLI uses --description/-d (not --body like gh CLI). Well-placed, concise, and follows the existing documentation pattern.
## AI Code Review
**LGTM** - This PR adds a helpful tip documenting that tea CLI uses --description/-d (not --body like gh CLI). Well-placed, concise, and follows the existing documentation pattern.
This is an automated review generated by the code-reviewer agent.
Summary
Clean documentation improvement that addresses a common usability issue when switching between gh and tea CLIs. The tip is well-formatted, concise, and appropriately placed.
Bold label + colon + description matches the pattern established by other tips
Appropriate use of backticks for CLI flags
Test Coverage
Not applicable (documentation change)
PR includes verification checklist in test plan
Verdict
LGTM - Ready to merge. This is a valuable addition that will help users avoid common mistakes when using tea CLI.
## AI Code Review
> This is an automated review generated by the code-reviewer agent.
### Summary
Clean documentation improvement that addresses a common usability issue when switching between gh and tea CLIs. The tip is well-formatted, concise, and appropriately placed.
### Findings
#### Code Quality
- Follows existing documentation formatting conventions perfectly
- Consistent with other tips in style and structure
- Concise and actionable wording
#### Potential Bugs
- No issues found
#### Security Concerns
- No issues found (documentation only)
#### Style Notes
- Perfectly consistent with existing tip format
- Bold label + colon + description matches the pattern established by other tips
- Appropriate use of backticks for CLI flags
#### Test Coverage
- Not applicable (documentation change)
- PR includes verification checklist in test plan
### Verdict
LGTM - Ready to merge. This is a valuable addition that will help users avoid common mistakes when using tea CLI.
This is an automated review generated by the code-reviewer agent.
Summary
This PR adds a helpful tip documenting the difference between tea CLI and gh CLI flag naming for PR descriptions. The change is well-placed, concise, and follows the existing documentation pattern.
Findings
Code Quality
Clear and actionable tip that follows the established format (bolded term followed by explanation)
Placement after the "View single issue" tip maintains logical grouping (both are command syntax clarifications)
Parenthetical comparison to gh CLI provides valuable context for users familiar with GitHub's CLI
Potential Bugs
No issues found (documentation change only)
Security Concerns
No issues found
Style Notes
Consistent with existing tip format in the Tips section
Uses the same pattern as the first tip (command clarification with "NOT" warning)
Proper markdown formatting with bold emphasis
Test Coverage
Not applicable for documentation changes
The test plan correctly identifies verification of placement in the Tips section
Verdict
LGTM - This is a valuable addition that will prevent user confusion when creating PRs with tea CLI. The tip is correctly formatted, well-placed, and addresses a real usability issue documented in #5.
## AI Code Review
> This is an automated review generated by the code-reviewer agent.
### Summary
This PR adds a helpful tip documenting the difference between tea CLI and gh CLI flag naming for PR descriptions. The change is well-placed, concise, and follows the existing documentation pattern.
### Findings
#### Code Quality
- Clear and actionable tip that follows the established format (bolded term followed by explanation)
- Placement after the "View single issue" tip maintains logical grouping (both are command syntax clarifications)
- Parenthetical comparison to gh CLI provides valuable context for users familiar with GitHub's CLI
#### Potential Bugs
- No issues found (documentation change only)
#### Security Concerns
- No issues found
#### Style Notes
- Consistent with existing tip format in the Tips section
- Uses the same pattern as the first tip (command clarification with "NOT" warning)
- Proper markdown formatting with bold emphasis
#### Test Coverage
- Not applicable for documentation changes
- The test plan correctly identifies verification of placement in the Tips section
### Verdict
**LGTM** - This is a valuable addition that will prevent user confusion when creating PRs with tea CLI. The tip is correctly formatted, well-placed, and addresses a real usability issue documented in #5.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
--description/-dflag for PR body content, not--bodylike gh CLITest plan
Closes #5
🤖 Generated with Claude Code
AI Code Review
LGTM - This PR adds a helpful tip documenting that tea CLI uses --description/-d (not --body like gh CLI). Well-placed, concise, and follows the existing documentation pattern.
AI Code Review
Summary
Clean documentation improvement that addresses a common usability issue when switching between gh and tea CLIs. The tip is well-formatted, concise, and appropriately placed.
Findings
Code Quality
Potential Bugs
Security Concerns
Style Notes
Test Coverage
Verdict
LGTM - Ready to merge. This is a valuable addition that will help users avoid common mistakes when using tea CLI.
AI Code Review
Summary
This PR adds a helpful tip documenting the difference between tea CLI and gh CLI flag naming for PR descriptions. The change is well-placed, concise, and follows the existing documentation pattern.
Findings
Code Quality
Potential Bugs
Security Concerns
Style Notes
Test Coverage
Verdict
LGTM - This is a valuable addition that will prevent user confusion when creating PRs with tea CLI. The tip is correctly formatted, well-placed, and addresses a real usability issue documented in #5.