// Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories
Guidelines for squashing old Canvas database migrations
Update Ruby gem dependencies
MUST use this skill when writing, reviewing, or modifying Ruby RSpec tests (*_spec.rb) in Canvas
Help create a well-formatted git commit message following Canvas LMS conventions
| name | ketchup |
| description | Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories |
I just cleared context. Help me ketchup by analyzing all uncommitted changes.
The script has gathered git status and diffs from the Canvas LMS main repository and all plugin subrepositories. Here's all the data:
!.claude/skills/ketchup/get-diffs.sh $ARGUMENTS
Analyze the repository changes above and provide a comprehensive summary:
Based on the nature of changes across all repositories, infer:
Determine if the changes are:
List the most important files being modified with their paths and relevant line numbers.
For example: app/models/user.rb:45-67
Based on incomplete work or patterns in the changes, suggest what the developer might work on next.
If commit information was requested and included, note which changes are already committed in addition to still uncommitted.
gems/plugins/* are separate git repositories/ketchup - Analyzes only uncommitted changes/ketchup commits - Analyzes both uncommitted changes and recent commits/ketchup some changes have been committed - Also includes commit analysis