Inline Comments
Get line-by-line feedback directly on the code that needs attention.
How It Works
When Jasper reviews your pull request, it identifies specific lines that need attention and posts comments directly on those lines in the GitHub diff view. This makes it easy to see exactly what needs to be addressed.
Types of Inline Comments
Inline comments are categorized by severity:
Must Fix
Security vulnerabilities, bugs that will cause failures
Should Fix
Performance issues, potential bugs, code smells
Consider
Improvements, best practices, style suggestions
Responding to Comments
You can reply to any inline comment to:
- Ask for clarification - "@jasper Can you explain this more?"
- Request alternatives - "@jasper What's a better approach?"
- Discuss the suggestion - "@jasper I think this is intentional because..."
Jasper will respond with context-aware answers based on the specific code being discussed.
Comment Structure
Each inline comment includes:
- Issue description - What the problem is
- Why it matters - The impact or risk
- Suggested fix - How to resolve it (often with code)
Code Suggestions
When applicable, Jasper provides code suggestions that you can apply directly in GitHub. These appear as "suggested changes" that you can commit with a single click.
Example suggested change:
```suggestion
// Use strict equality instead of loose equality
if (user.id === currentUserId) {
```Best Practices
- Address critical issues first - Focus on security and bugs before style
- Use the conversation - Don't hesitate to ask Jasper for more context
- Apply suggestions - Use GitHub's "Commit suggestion" feature when the fix looks good
- Learn from patterns - Note recurring suggestions to improve your coding habits