A PR title goes in the imperative, like a commit message: Add retry to payment webhook, not Added or Adding. In the description, use the sections What, Why and How to test.
Easy phrases (124)
I opened a pull request for the new feature.
When to use it: Informing the team that you submitted a PR
Can you review my pull request when you get a chance?
When to use it: Politely asking a colleague to review your PR
I approved your pull request.
When to use it: Letting someone know their PR has been approved
This PR is ready to merge.
When to use it: Indicating that a pull request has all approvals and can be merged
I left a few comments on your PR.
When to use it: Notifying someone that you provided review feedback
Please add a description to the pull request.
When to use it: Asking someone to provide context in their PR description
The build is failing on this pull request.
When to use it: Reporting that CI checks are not passing for a PR
This change looks good to me. LGTM!
When to use it: Approving a PR with the common shorthand LGTM (Looks Good To Me)
I requested changes on the pull request.
When to use it: Informing someone you left feedback requiring modifications
I've marked this PR as ready for review.
When to use it: Converting a draft PR to a review-ready state
The linter is complaining about unused imports
When to use it: Fixing code quality issues
Nice refactor, the code is much cleaner now
When to use it: Positive review feedback
I've updated the PR description with more context
When to use it: Improving PR documentation
This PR closes issue #247
When to use it: Linking PR to an issue
The review is taking longer than expected, sorry for the delay
When to use it: Apologizing for slow review
I've added screenshots of the UI changes to the PR description
When to use it: Documenting visual changes
I noticed some dead code that could be removed in this file
When to use it: Suggesting cleanup
I've added inline comments explaining the tricky parts
When to use it: Self-documenting complex code
The PR has been approved, waiting for the green build to merge
When to use it: PR in queue to merge
I've tagged this PR with the correct milestone
When to use it: Organizing PRs by release
I've bumped the version number in preparation for the release
When to use it: Release preparation
I've linked the related PRs in the description for context
When to use it: Providing review context
The before and after screenshots show a clear improvement
When to use it: Reviewing visual changes
I've added a TODO comment for the follow-up work
When to use it: Marking future work
The variable naming could be more descriptive here
When to use it: Suggesting better readability
I'll batch these small fixes into a single PR
When to use it: Consolidating minor changes
Great job keeping this PR focused and well-scoped
When to use it: Praising good PR practices
I've resolved the conversation threads in the review
When to use it: Marking discussions as addressed
Approved with minor suggestions, feel free to merge
When to use it: Giving conditional approval
I tagged the tech lead as a required reviewer.
When to use it: Assigning reviewers
The code coverage increased by 5% with this PR.
When to use it: Sharing quality metrics
I linked the Jira ticket to the PR for traceability.
When to use it: Organizing work
I added a changeset file for the version bump.
When to use it: Describing release prep
Can you run the manual test suite on this branch?
When to use it: Requesting manual testing
The PR template reminds us to check for breaking changes.
When to use it: Referencing process
I'm updating the types to match the new API contract.
When to use it: Describing type safety work
Please test this on the latest version of Safari before approving.
When to use it: Setting review conditions
I noticed the error messages are not localized in this change.
When to use it: Flagging missing requirement
The branch is behind main by 30 commits, please rebase.
When to use it: Requesting rebase
This code could benefit from some inline documentation.
When to use it: Suggesting improvement
The failing test is unrelated to my changes, it's a known flaky test.
When to use it: Explaining CI failure
I moved the helper functions to a shared utilities file.
When to use it: Describing code organization
The CI is green and all review comments have been addressed.
When to use it: Confirming readiness
I added validation to prevent empty strings from being saved.
When to use it: Describing validation
The PR was auto-closed by the stale bot, I'll reopen it.
When to use it: Managing PR lifecycle
I marked the review threads as resolved after pushing the fixes.
When to use it: Managing review threads
Could you add a comment explaining why this null check is needed?
When to use it: Requesting documentation
The CI checks are mandatory, we can't skip them even for hotfixes.
When to use it: Enforcing process
I removed the unused dependency that was increasing the build time.
When to use it: Describing cleanup
This PR addresses the feedback from the design review.
When to use it: Describing context
I'll add a follow-up PR to handle the remaining edge cases.
When to use it: Planning follow-up work
Could you verify the dark mode styles are correct in this PR?
When to use it: Requesting visual review
I added a changelog entry describing the new feature.
When to use it: Documenting changes
I included the API documentation updates alongside the code changes.
When to use it: Describing completeness
The PR is waiting on the design team's approval for the UI changes.
When to use it: Sharing blocker
I ran the accessibility audit and all checks pass.
When to use it: Reporting quality check
The feature flag cleanup PR can be merged after the full rollout.
When to use it: Planning flag removal
Could you double-check the error codes match the specification?
When to use it: Requesting specific review
I added a retry button for failed network requests.
When to use it: Describing UX improvement
The code review guidelines say we should avoid magic numbers.
When to use it: Referencing guidelines
I updated the mock data to reflect the new API response format.
When to use it: Describing test update
I need a reviewer who's familiar with the payment processing flow.
When to use it: Requesting specific expertise
The PR diff is smaller than it looks, most changes are auto-generated.
When to use it: Setting expectations for review
I extracted the constants into a separate configuration file.
When to use it: Describing code organization
I've tested all the permutations of the form validation.
When to use it: Reporting thorough testing
The auto-merge will kick in once the required checks pass.
When to use it: Explaining merge automation
I added a TODO with a tracking issue for the remaining work.
When to use it: Documenting follow-up
I renamed the method to better reflect its purpose.
When to use it: Describing readability improvement
Can we use early returns to avoid deep nesting?
When to use it: Suggesting code improvement
The commit message should reference the issue number.
When to use it: Enforcing conventions
The review comments are all resolved, requesting re-review.
When to use it: Moving review forward
This switch statement should have a default case for safety.
When to use it: Suggesting defensive coding
I replaced the force unwrap with a safe optional binding.
When to use it: Improving code safety
I inlined the one-line function since it was only used once.
When to use it: Justifying simplification
This access modifier should be internal, not public.
When to use it: Flagging visibility issue
The optional chaining handles the nil case gracefully.
When to use it: Explaining Swift pattern
The test assertion message should describe what went wrong.
When to use it: Improving test quality
I grouped the related changes into separate commits for clarity.
When to use it: Describing commit organization
I configured the merge strategy to squash all commits into one.
When to use it: Describing merge configuration
The animation improvements are subtle but make the app feel more polished.
When to use it: Describing UX improvement
This extension adds convenience methods that simplify common operations.
When to use it: Justifying code addition
The review bot detected unused code that should be removed.
When to use it: Reporting automated finding
I added a PR label to indicate this needs a design review.
When to use it: Using labels effectively
This PR is part of a series, please review them in order.
When to use it: Setting review expectations
I've written a comprehensive test plan in the PR description.
When to use it: Documenting testing approach
The PR changelog covers all the user-facing changes.
When to use it: Ensuring completeness
I added a code comment explaining the workaround for the SDK bug.
When to use it: Documenting workarounds
The localization strings are missing for the new error messages.
When to use it: Flagging missing translations
I updated the padding values to match the design specifications.
When to use it: Describing UI fix
This enum case naming doesn't follow our convention, can we rename it?
When to use it: Enforcing naming conventions
The animation curve needs adjustment, it feels too abrupt.
When to use it: Providing UX feedback
This string concatenation should use string interpolation instead.
When to use it: Suggesting Swift idiom
I used the Codable protocol to simplify JSON parsing.
When to use it: Describing Swift approach
I increased the touch target size to meet the 44pt minimum.
When to use it: Describing accessibility fix
This color literal should use the design system constant instead.
When to use it: Enforcing design system
I added haptic feedback for the button press to improve the feel.
When to use it: Describing UX improvement
The loading state needs a skeleton view instead of a plain spinner.
When to use it: Suggesting UI improvement
The PR preview link shows exactly how the changes look in the app.
When to use it: Pointing to visual evidence
I replaced the hardcoded spacing values with design system tokens.
When to use it: Enforcing design system
The transition animation should use the standard spring curve.
When to use it: Suggesting animation improvement
I grouped the related UI components into a separate Swift file.
When to use it: Describing code organization
This preview provider needs sample data to render correctly.
When to use it: Identifying missing requirement
I added a loading shimmer effect to match the design system.
When to use it: Describing UI implementation
The empty state view needs a call-to-action button.
When to use it: Suggesting UX improvement
This PR is safe to merge anytime, it has no user-visible impact.
When to use it: Clarifying merge safety
I updated the unit tests to cover the new validation rules.
When to use it: Describing test coverage
This PR introduces the new design for the settings screen.
When to use it: Describing visual change
I added the VoiceOver labels for all interactive elements.
When to use it: Describing accessibility work
This change was requested by the product team to improve retention.
When to use it: Providing business context
I verified the PR works on both light and dark mode.
When to use it: Reporting visual testing
I added error handling for the network timeout scenario.
When to use it: Describing resilience
The keyboard handling needs to be tested on all device sizes.
When to use it: Setting test requirements
I wrapped the throwing call in a do-catch block.
When to use it: Describing error handling
The image assets should use the 2x and 3x variants.
When to use it: Flagging asset requirement
I added the appropriate content description for the image views.
When to use it: Describing accessibility
The view model should conform to ObservableObject for SwiftUI data flow.
When to use it: Explaining SwiftUI requirement
I created a reusable card component to avoid duplicating the layout.
When to use it: Describing component extraction
I tested the pull request on iPad to verify the split view layout.
When to use it: Reporting device testing
This PR is ready for QA to start testing on TestFlight.
When to use it: Announcing readiness
I extracted the date formatting logic into a dedicated extension.
When to use it: Describing code organization
I used the SF Symbols to keep the icon style consistent.
When to use it: Describing design choice
The App Store review guidelines require us to add a privacy policy link.
When to use it: Flagging compliance requirement
I verified the PR passes all the accessibility audit checks.
When to use it: Reporting compliance
This PR ships the minimum viable version, we'll iterate in follow-ups.
When to use it: Setting expectations
Intermediate phrases (117)
I'll merge this after the CI pipeline passes.
When to use it: Waiting for automated tests to finish before merging
There are merge conflicts that need to be resolved.
When to use it: Pointing out that a PR has conflicts with the target branch
Could you squash the commits before merging?
When to use it: Requesting that multiple commits be combined into one before merge
I created a draft pull request for early feedback.
When to use it: Opening a work-in-progress PR to get initial input from the team
Can you rebase your branch on top of main?
When to use it: Asking someone to update their branch with the latest changes from main
I addressed all the review comments and pushed the changes.
When to use it: Letting reviewers know you have incorporated their feedback
Let's split this PR into smaller, more focused changes.
When to use it: Suggesting that a large PR be broken down for easier review
I think we should add unit tests to cover this change.
When to use it: Suggesting that test coverage is needed for the PR changes
Can we get one more approval before merging this?
When to use it: Requesting an additional review approval for safety
Could you add a screenshot to the PR showing the UI change?
When to use it: Requesting visual evidence of frontend changes in the PR description
The CODEOWNERS file auto-assigns reviewers based on the changed paths
When to use it: Explaining how automatic reviewer assignment works
I need to cherry-pick that commit into the hotfix branch
When to use it: Selecting a specific commit to apply to another branch
The PR template is missing the testing checklist section
When to use it: Noting that the PR description is incomplete
I left a couple of nit-picks, nothing blocking
When to use it: Minor review feedback
I added inline comments directly on the diff to explain my reasoning
When to use it: Leaving contextual notes on specific lines in the PR
I converted the draft PR to ready for review after finishing the tests
When to use it: Changing PR status from draft to open
There's a merge conflict in the config file
When to use it: Reporting conflicts
Can you request a second reviewer for this critical change?
When to use it: Asking for an additional review on important code
Could you add unit tests for the new helper function?
When to use it: Requesting test coverage
I need at least two approvals before merging
When to use it: Following branch protection rules
Let's set up an A/B test to measure the impact of this new flow
When to use it: Proposing to test the new behavior with a subset of users
The PR template is missing the test plan section
When to use it: Ensuring completeness
I'm going to force-push to clean up the commit history
When to use it: Rewriting branch history
Let's hold off on merging until after the release
When to use it: Timing merge with release cycle
This looks like it could be a separate utility function
When to use it: Suggesting code extraction
Great catch on that edge case, I've added a test for it
When to use it: Responding to review feedback positively
I've resolved the merge conflicts and pushed a new commit
When to use it: After resolving conflicts
Auto-merge is enabled, it will merge once checks pass
When to use it: Setting up automatic merge
The diff is really hard to read, can you restructure the changes?
When to use it: Asking for better organization
I dismissed the stale review since the code has changed significantly
When to use it: Removing an outdated review that no longer applies
Make sure to update the API documentation with these changes
When to use it: Reminding about docs
The code review checklist hasn't been completed yet
When to use it: Ensuring review process compliance
I've pinged the codeowners for this directory
When to use it: Requesting required reviewers
Can you verify this works on both iOS and Android?
When to use it: Requesting cross-platform testing
I've separated the refactoring from the feature changes into two PRs
When to use it: Splitting work for easier review
The stale bot is about to close this PR, should we keep it?
When to use it: Managing abandoned PRs
Please make sure the environment variables are documented
When to use it: Ensuring operational readiness
I've reverted the accidental commit and pushed the correction
When to use it: Fixing mistakes
This introduces a new shared component that other teams can use
When to use it: Creating reusable code
I'm going to close this PR and open a fresh one with a better approach
When to use it: Starting over with improved solution
The naming convention doesn't match our style guide
When to use it: Enforcing coding standards
This commit should have been in a separate PR
When to use it: Suggesting better organization
I've extracted the shared logic into a common module
When to use it: Improving code reuse
This PR supersedes the previous attempt at fixing this bug
When to use it: Replacing an older PR
I've verified the fix manually on all supported browsers
When to use it: Confirming cross-browser testing
The PR is blocked by branch protection rules
When to use it: Explaining why merge is prevented
The commit message doesn't follow our conventional commits format
When to use it: Enforcing commit conventions
We need to coordinate this merge with the backend team
When to use it: Cross-team coordination
I've converted this to a draft PR while I work out the remaining issues
When to use it: De-prioritizing an incomplete PR
This would be a great opportunity to improve our error messages
When to use it: Suggesting enhancement during review
Let me re-request review after pushing the latest changes
When to use it: Updating reviewers after changes
We should avoid mixing formatting changes with logic changes
When to use it: PR best practices
I need to add a database migration before this can be merged.
When to use it: Identifying prerequisite
This PR removes the deprecated endpoints we discussed last sprint.
When to use it: Describing cleanup
The end-to-end tests are taking too long on this PR.
When to use it: Identifying CI issue
I included the before and after benchmarks in the description.
When to use it: Providing evidence
This PR fixes a critical security vulnerability.
When to use it: Flagging urgency
I refactored the error handling to use a centralized approach.
When to use it: Describing improvement
This PR adds the new GraphQL mutation for user preferences.
When to use it: Describing feature
I tested the migration rollback and it works correctly.
When to use it: Reporting verification
The PR needs a sign-off from the security team.
When to use it: Identifying approval requirement
I'm adding feature toggles to safely deploy this behind a flag.
When to use it: Describing deployment strategy
I used a revert commit instead of force-pushing to preserve history.
When to use it: Explaining git approach
This change requires a corresponding update to the mobile app.
When to use it: Flagging cross-platform dependency
I need to add an index before this query change can be deployed.
When to use it: Identifying deployment prerequisite
The test matrix covers all the supported browser versions.
When to use it: Describing test coverage
The memory usage improved significantly after this optimization.
When to use it: Sharing performance metrics
This PR consolidates the duplicate validation logic into one place.
When to use it: Describing DRY improvement
I verified the backward compatibility with the previous API version.
When to use it: Reporting verification
This migration needs to run during the maintenance window.
When to use it: Flagging deployment constraint
This PR standardizes the logging format across all microservices.
When to use it: Describing standardization
This abstraction makes the code more testable.
When to use it: Justifying design choice
I simplified the conditional logic to reduce cognitive complexity.
When to use it: Describing refactoring
I used guard clauses to handle the edge cases at the top.
When to use it: Explaining code structure
I replaced the class with a struct since it doesn't need reference semantics.
When to use it: Explaining Swift design choice
This singleton should be lazily initialized to avoid startup delays.
When to use it: Suggesting performance improvement
I added proper error propagation instead of swallowing the exception.
When to use it: Improving error handling
The dependency injection makes this component easier to test.
When to use it: Justifying architecture
I moved the business logic out of the view controller.
When to use it: Describing MVVM improvement
This protocol extension provides default implementations for common methods.
When to use it: Describing Swift pattern
The computed property is recalculated every time, should we cache it?
When to use it: Questioning performance
I added the async keyword to support the new concurrency model.
When to use it: Describing API change
I made the initializer failable to handle invalid input.
When to use it: Describing defensive design
I refactored the callback to use a completion handler pattern.
When to use it: Describing API improvement
This view modifier encapsulates the shared styling logic.
When to use it: Describing SwiftUI pattern
The binding is two-way, changes in the child propagate to the parent.
When to use it: Explaining data flow
This environment key lets child views access the shared state.
When to use it: Explaining SwiftUI pattern
I used a Result type instead of throwing to make error handling explicit.
When to use it: Explaining error handling approach
I set up the PR to auto-deploy to the preview environment.
When to use it: Describing CI/CD setup
The API response time decreased from 400ms to 120ms with this change.
When to use it: Sharing concrete metrics
I used the builder pattern to make the configuration more readable.
When to use it: Justifying design pattern
I separated the concerns by creating a dedicated service layer.
When to use it: Describing architecture
I replaced the notification observer with a Combine subscriber.
When to use it: Describing modernization
The test data should be generated randomly to catch more edge cases.
When to use it: Improving test strategy
This navigation logic should live in the coordinator, not the view.
When to use it: Suggesting architecture improvement
I converted the imperative code to a declarative SwiftUI approach.
When to use it: Describing modernization
The font sizes need to scale with Dynamic Type for accessibility.
When to use it: Flagging accessibility requirement
I moved the color definition to the asset catalog for dark mode support.
When to use it: Describing theme support
This view should use @StateObject instead of @ObservedObject for ownership.
When to use it: Correcting SwiftUI usage
I made the view model testable by injecting the dependencies.
When to use it: Describing testability improvement
This layout breaks on smaller screen sizes, we need a responsive design.
When to use it: Flagging layout issue
I implemented the feature with backward compatibility for iOS 17.
When to use it: Describing compatibility
The state restoration logic ensures the user's progress is preserved.
When to use it: Describing feature
I validated the input using a regex pattern to prevent injection.
When to use it: Describing security measure
This PR fixes the layout glitch that occurs during rotation.
When to use it: Describing UI fix
This PR deprecates the old API and adds migration documentation.
When to use it: Managing API lifecycle
This PR adds deep link support for the onboarding flow.
When to use it: Describing feature addition
I used @Published with a private setter to prevent external mutations.
When to use it: Explaining access control
The scrolling performance is laggy, we should use lazy loading.
When to use it: Identifying performance issue
This PR consolidates the networking layer into a single module.
When to use it: Describing architecture change
I used the @MainActor attribute to ensure UI updates happen on the main thread.
When to use it: Describing thread safety
The gesture recognizer conflicts with the scroll view, I added a priority.
When to use it: Describing gesture handling fix
I ensured the animations are disabled during UI tests.
When to use it: Describing test optimization
The PR automatically triggers a TestFlight build when merged to main.
When to use it: Describing CI/CD automation
This PR includes the widget extension changes alongside the main app update.
When to use it: Describing scope
I added a migration path for users upgrading from the previous version.
When to use it: Describing upgrade support
I added the crash reporting integration to track production issues.
When to use it: Describing observability
Advanced phrases (59)
The PR description should explain the motivation behind the change.
When to use it: Asking for better context in a PR to help reviewers understand why the change was made
I'll resolve the conflicts and force-push the updated branch.
When to use it: Stating your plan to fix merge conflicts and update the remote branch
I noticed a potential performance issue in this diff.
When to use it: Pointing out a performance concern during code review
This PR introduces a breaking change to the public API.
When to use it: Warning that the PR changes will break existing consumers of the API
We should avoid merging this until the dependent PR is merged first.
When to use it: Pointing out a dependency between two pull requests
The linter is flagging some style issues that need to be fixed.
When to use it: Noting that automated style checks found problems in the PR
I suggest using a feature flag to safely roll out this change.
When to use it: Recommending a gradual rollout approach for a risky change
Let me walk you through the changes in this pull request.
When to use it: Offering to explain the PR changes to reviewers in a meeting or comment
I reverted the PR because it caused a regression in production.
When to use it: Explaining why a previously merged PR was rolled back
The code coverage dropped after these changes. Can we add more tests?
When to use it: Noting that test coverage decreased and requesting additional tests
This PR touches over fifty files, it's hard to review thoroughly
When to use it: Expressing concern about a PR that changes too many files
I used interactive rebase to reorder and clean up the commits
When to use it: Using git rebase -i to tidy commit history before review
We need to ensure backward compatibility with the previous endpoint
When to use it: Discussing the need to support older API consumers
The mutation testing report shows several surviving mutants in this module
When to use it: Reviewing mutation testing results to assess test quality
Can you cherry-pick this fix to the release branch?
When to use it: Requesting a targeted fix
I'll mark this as a breaking change in the changelog
When to use it: Documenting impact
This introduces a circular dependency between modules
When to use it: Identifying architecture issues
This migration needs to be backwards compatible
When to use it: Ensuring safe database changes
Can we get a second pair of eyes on the security implications?
When to use it: Requesting security review
The automated review bot flagged some complexity issues
When to use it: Addressing static analysis findings
The type definitions need to be exported for downstream consumers
When to use it: Discussing API surface
We should run performance benchmarks before merging this
When to use it: Requesting performance validation
I've marked the PR as blocked until the dependency is updated
When to use it: Indicating a PR is on hold
This needs a database migration script alongside the code changes
When to use it: Ensuring complete delivery
This hotfix PR needs to bypass the normal review process
When to use it: Expediting urgent fixes
The integration tests are passing locally but failing in CI
When to use it: Debugging environment differences
This is a follow-up PR to address the tech debt we discussed
When to use it: Linking to previous discussions
The race condition in the test is causing flaky failures
When to use it: Debugging unreliable tests
The accessibility review flagged missing aria labels
When to use it: Addressing a11y issues
The dependency update PR needs careful testing for regressions
When to use it: Warning about risky changes
Can you explain the reasoning behind this architectural decision?
When to use it: Asking for justification
This error handling needs to be more granular
When to use it: Requesting better error management
Merging this will unblock three other PRs that depend on it
When to use it: Prioritizing impactful merges
The rollback strategy needs to be defined before we ship this
When to use it: Ensuring safe deployment
Can you check if this change is backwards compatible with v2?
When to use it: Verifying compatibility
The snapshot tests need to be regenerated after this UI change
When to use it: Maintaining visual regression tests
The type safety improvements in this PR are really solid
When to use it: Praising quality work
This change touches a critical path, let's get extra reviewers
When to use it: High-risk review request
The Dependabot PR for the security patch should be prioritized
When to use it: Handling automated security updates
This PR implements the retry mechanism with exponential backoff.
When to use it: Describing implementation
This PR reduces the bundle size by 15% through tree shaking.
When to use it: Sharing optimization results
This function should be pure — it's modifying state as a side effect.
When to use it: Flagging code smell
This PR introduces a new caching layer to reduce database load.
When to use it: Describing architecture change
This PR closes a long-standing race condition in the event handler.
When to use it: Describing significant fix
I rewrote the SQL query to avoid the full table scan.
When to use it: Describing optimization
This generic type constraint helps catch type errors at compile time.
When to use it: Explaining type safety
I'm concerned about the thread safety of this implementation.
When to use it: Flagging concurrency issue
I wrapped the async call in a task group for better concurrency.
When to use it: Describing concurrency approach
This weak reference prevents a retain cycle between the delegate and the view.
When to use it: Explaining memory management
I added a custom Equatable conformance to optimize diff calculations.
When to use it: Describing performance optimization
I replaced the timer with a Combine publisher for better lifecycle management.
When to use it: Describing reactive approach
The property wrapper handles the UserDefaults persistence transparently.
When to use it: Explaining Swift pattern
This actor ensures thread-safe access to the shared mutable state.
When to use it: Describing concurrency pattern
This refactoring reduces the cyclomatic complexity from 15 to 6.
When to use it: Sharing concrete improvement
This closure should capture self weakly to avoid a memory leak.
When to use it: Flagging memory issue
This async sequence handles backpressure automatically.
When to use it: Describing concurrency feature
I used a diffable data source for better list performance.
When to use it: Describing implementation choice
I replaced the dispatch queue with structured concurrency.
When to use it: Describing modernization
I optimized the view hierarchy to reduce overdraw.
When to use it: Describing performance fix
Other everyday developer situations
- Daily standup280 phrases
- Code review275 phrases
- Bug reports300 phrases
- Meetings300 phrases
- Job interviews300 phrases
- Slack and chat300 phrases
- Email298 phrases
- Technical discussions299 phrases
- Polite phrases300 phrases
- Pair programming300 phrases
- Documentation300 phrases
Guides with more context
Take it to your phone
In the Devlingo app you get 10 new phrases a day, each with real-world context, pronunciation and examples, and the widget shows the phrase of the day on your iPhone Home Screen.