Add screenshot placeholders and restructure token setup documentation#281
Add screenshot placeholders and restructure token setup documentation#281albertov19 merged 9 commits intomainfrom
Conversation
Add TODO placeholders at the steps where users are most likely to get stuck during token creation: GitLab (2 screenshots): - Step 3: Legacy vs Fine-grained token type selection dropdown - Step 4: Token form with name, expiration, and required scopes Bitbucket (2 screenshots): - Step 4: Product selection page with Bitbucket chosen - Step 5: Scopes page with all 14 required permissions checked Images will be added as .webp files in a follow-up commit once the screenshots are taken. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace the vague one-liner about feedback with two concrete paths: - IDE: open Recent Reviews in the extension sidebar, click a review, use thumbs up/down on individual issues - Platform: open Review History, click a review, use the Your Feedback section with Yes/No rating and optional comments Add screenshot placeholders for both the IDE feedback buttons and the platform Your Feedback section. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add two screenshots to the GitLab "Create an access token" section: - Step 3: Token type selection dropdown showing Legacy token vs Fine-grained token (Beta) - Step 4: Legacy token form with name, expiration date, and required scopes (api, read_api, read_user) selected Remove TODO placeholder comments now that the actual images are in place. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Bitbucket offers two API token methods, similar to GitLab's Legacy vs Fine-grained distinction. Restructure the "Create an API token" section to: - Make "Create API token" (simple) the primary recommended path: name + expiration + Create. No scope selection needed. - Move "Create API token with scopes" into a collapsed details block with the full 4-step wizard (name/expiry, select app, select scopes, create) and the 14-scope reference table - Add 1 screenshot placeholder for the simple path (API Tokens page showing both creation options) - Match the GitLab page pattern: recommended path visible, alternative collapsed Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add screenshot to step 3 of the simple "Create API token" path showing the creation dialog with name, expiration date, and Create button. Remove the TODO placeholder comment. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add two screenshots to the "How can I provide feedback" FAQ entry: - IDE: Review Details panel showing an expanded issue with thumbs up/down feedback buttons alongside Snooze and Ignore actions - Platform: Review History detail page showing the Your Feedback section with Yes/No rating buttons and optional comments field Remove TODO placeholder comments now that the actual images are in place. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
albertov19
added
A2 - Maintenance Minor
🤖 kluster.ai PR Review Summary⚡ Review this PR in 1/10 of the time — Try our new AI-powered code review experience 📋 PR SummaryThis PR updates documentation for kluster.ai code reviews and integrations with Bitbucket and GitLab. It clarifies how to provide feedback on code review results from the IDE or kluster.ai platform, and adds instructions for creating API tokens for Bitbucket and GitLab, including screenshots to illustrate the process. The changes aim to improve user understanding of how to interact with kluster.ai's code review features and how to set up integrations with their version control platforms. ✅ All ClearNo issues detected in this PR.
Powered by kluster.ai - Real-Time AI code review in your IDE |
There was a problem hiding this comment.
Pull request overview
Updates kluster.ai Code Reviews documentation to make feedback workflows clearer and to reflect updated token-creation flows for Bitbucket and GitLab, adding supporting screenshots.
Changes:
- Expanded FAQ instructions for submitting review feedback from both the IDE and the kluster.ai platform, with screenshots.
- Restructured Bitbucket API token setup to distinguish “standard” vs “scoped” token creation, with an alternative scoped-token section and screenshots.
- Updated GitLab token setup steps to match the newer token UI and added screenshots.
Reviewed changes
Copilot reviewed 3 out of 8 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
code-reviews/pr-reviews/gitlab.md |
Updates Legacy token creation step wording and adds screenshots for token type selection + scope selection. |
code-reviews/pr-reviews/bitbucket.md |
Reworks token creation section into recommended “standard token” path + alternative scoped-token wizard path, adding a screenshot. |
code-reviews/faq.md |
Adds step-by-step feedback instructions for IDE and platform, with screenshots. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The Legacy path says "click Generate token" but the fine-grained alternative still referenced "Add new token". Update to "Generate token" so both paths use the same button label matching the current GitLab UI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Prerequisites and the section intro said "with the api scope" while step 4 listed all three (api, read_api, read_user). Update both locations to list all three scopes so the requirement is consistent throughout the page. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
🤖 kluster.ai PR Review Summary⚡ Review this PR in 1/10 of the time — Try our new AI-powered code review experience 📋 PR SummaryThis PR updates documentation for kluster.ai, focusing on improving instructions for providing feedback on code reviews and creating API tokens for Bitbucket and GitLab integrations. It enhances the FAQ by detailing how to provide feedback from both the IDE and the kluster.ai platform, with accompanying screenshots. The PR reviews documentation for Bitbucket and GitLab is also updated to clarify the process of creating API tokens, including the recommended methods and alternative approaches, along with new images to illustrate the steps. These changes aim to make the setup and usage of kluster.ai more straightforward and user-friendly. ✅ All ClearNo issues detected in this PR.
Powered by kluster.ai - Real-Time AI code review in your IDE |
Description
This pull request updates the documentation for providing feedback on code reviews and clarifies the setup steps for integrating kluster.ai with Bitbucket and GitLab. The changes focus on making instructions more user-friendly, adding visual aids, and clarifying the distinctions between different token creation methods.
Feedback workflow improvements:
Bitbucket integration instructions:
GitLab integration instructions:
Checklist
kluster-mkdocsrepo