5 exercises on the verb collocations developers use at the start of each working day. Choose the right verb for the right context.
Key verb patterns
check the CI dashboard / the pipeline / the build status
pull the latest changes (git vocabulary, not "sync" or "download")
triage notifications / issues — sort by urgency, not just read
check open PRs — checking the list vs. review a PR (reading the diff)
prioritise the day's work — order by importance/impact
0 / 5 completed
1 / 5
A developer starts their day by looking at the status board that shows build results and test outcomes. Which collocation correctly describes this action?
Check — the natural collocating verb for dashboards and status:
Check collocates naturally with dashboard, pipeline, status, results, and logs. It implies purposeful inspection — you are verifying the current state of something.
Why not the others?
read implies text-heavy content you read from start to finish, like a document or report
scan implies a quick, superficial glance — acceptable informally ("I scanned the dashboard") but less idiomatic for the deliberate morning habit
open describes the browser or app action, not the cognitive checking action
Core collocations with "check":
check the CI dashboard / check the pipeline
check the build status / check for failures
check the logs / check the metrics
check error rates / check the deployment
In daily standup: "I checked the CI and we have two failing builds from overnight." This is the standard opener for a developer morning routine.
2 / 5
A developer sits down and wants to make sure their local codebase matches the latest team changes. Which phrase is most natural in git vocabulary?
Pull — the precise git verb for fetching and integrating changes:
Pull is the exact and natural verb because it maps directly to the git command: git pull runs git fetch (download from remote) followed by git merge (integrate into current branch). It is both the technical term and the conversational word.
Why not the others?
download is too generic — it describes fetching data but not the git-specific integration step
get is informal and understood, but not precise in a git context
sync is used in GUI tools like GitHub Desktop and some other VCS systems (Perforce, SVN) but is not standard git CLI vocabulary
Related git collocations:
pull the latest / pull from origin / pull from main
git pull --rebase — reapply your commits on top of fetched changes
pull request (PR) — despite the name, this is a request to merge, not a git pull
Morning sequence: pull the latest changes → check for conflicts → run the tests.
3 / 5
A developer reads through their issue tracker, Slack messages, and email to decide what needs immediate attention versus what can wait. Which phrase precisely describes this action?
Triage — the precise word for sorting by priority and urgency:
Triage (from medical French — the sorting of patients by urgency of need) is the precise collocation for sorting through notifications, issues, emails, and alerts to determine which need immediate action, which can wait, and which can be dismissed entirely.
Why not the others?
answer implies responding to everything — but triage is specifically about deciding what deserves a response and when
check describes the act of looking, not the prioritisation decision
read describes the cognitive action, not the sorting/prioritisation process
triage the backlog — sorting old items by current priority
The triage mindset: P0 (handle now), P1 (handle today), P2 (schedule this week), dismiss (noise). In Agile: sprint triage, bug triage meeting, triage queue.
4 / 5
A team lead asks a developer to look at the list of open pull requests that are waiting for someone to review them. Which phrase is most natural?
Check open PRs — the morning habit collocation:
Check open PRs is the most natural phrase for the morning habit of reviewing the PR dashboard to see what needs your attention. "Check" here means inspecting the list — not doing the code review itself.
Why not the others?
review your open PRs — "review" specifically means doing a thorough code review (reading the diff, leaving comments, approving). Checking the list and doing a review are two different actions.
scan for open PRs — "scan for" implies searching for something you might not find; PRs are visible on the dashboard
look at the PR queue — informal and understood, but "check" is more natural
The morning PR workflow:
check open PRs → see who has assigned you as reviewer
pick up a PR to review → read the diff, run the code locally
request changes or approve → leave feedback or click Approve
Related: check the PR queue, check for assigned reviews, check requested reviews, check PR status.
5 / 5
In a team standup, a developer explains how they plan to order their tasks for maximum impact. Which collocation is most professional and precise?
Prioritise — the Agile/professional verb for ordering by importance:
Prioritise the day's work is the professional collocation in Agile and developer environments. It implies actively choosing which tasks to tackle first based on importance, urgency, and impact — not just listing or organising them.
Why not the others?
plan — vaguer; planning is about deciding what to do, not about ordering by importance
organise — implies structuring or grouping tasks, not necessarily ranking them by priority
schedule — implies calendar time-blocking (9am–10am: task A); more appropriate for calendar management than backlog ordering
Prioritise collocations in developer context:
prioritise the backlog / prioritise tasks / prioritise by impact
deprioritise — to move something down the list ("Let's deprioritise the refactor")
re-prioritise — to reorder after new information ("The P0 bug means we need to re-prioritise")
In standup: "I'm going to prioritise the migration ticket today because it's blocking the release."