Capture two web pages or image files for a visual comparison. Choose a page element with a CSS selector, set a mobile, tablet, or custom viewport, and create a Markdown comparison for PRs when needed.
- Compare UI before and after a change
- Capture a specific page element
- Prepare screenshot evidence for a PR
michaelshimeles/rstack☆ 1.4KUpdated Oct 26, 2026
Use this guide to decide when repeated operational code should become a shared service, while keeping product rules in the workflow actions that own them. It provides practical design principles and a gradual migration checklist to preserve existing boundaries and behavior.
- Deciding whether duplicated workflow code should be extracted
- Separating business rules from reusable operations
- Planning a gradual refactor across multiple callers
michaelshimeles/rstack☆ 1.4KUpdated Oct 26, 2026
Verify changed behavior with evidence suited to the task: a live screen recording for interactive UI flows, scripted captures for headless checks, or measured outputs for non-UI changes. Create a results report and send the evidence to the requested destination when authorized.
- Capturing a live recording of a UI test
- Checking a UI flow in a headless environment
- Comparing measured API or performance results
michaelshimeles/rstack☆ 1.4KUpdated Oct 26, 2026
Review Greptile feedback on a pull request, merge request, or shelved changelist, then make scoped fixes and request fresh reviews within a set cycle limit. Track actionable findings and report the current score, checks, and any work left unresolved.
- Working through Greptile feedback on a pull request
- Fixing actionable review findings on a merge request
- Reviewing a Perforce changelist with Greptile
michaelshimeles/rstack☆ 1.4KUpdated Oct 26, 2026
Run the existing `greploop` workflow with the `@greptile-apps` trigger when the usual trigger cannot handle a large pull request. This entrypoint depends on the separate `greploop` skill and adds no workflow of its own.
- Run greploop on a large PR
- Use the Greptile Apps trigger
- Continue an existing greploop review
michaelshimeles/rstack☆ 1.4KUpdated Oct 26, 2026
Prepare an isolated Git worktree and branch for each feature, fix, or documentation task. Check for an existing assignment and overlapping pull requests first, so edits stay scoped to the right work and do not build on another task’s changes.
- Starting a feature in its own worktree
- Fixing a bug without editing the shared checkout
- Checking for overlapping pull request changes
michaelshimeles/rstack☆ 1.4KUpdated Oct 26, 2026