Code open-text survey answers into consistent categories with a clear coding frame.
Skills tagged “code”
Check that a change to one platform, such as web or mobile, has the matching change on the others.
Check that errors from async tasks are reported and not lost.
Check that a pull request description states the goal, approach, risks and how it was tested.
Review changes to nullable columns for code that assumes a value is always present.
Review changes to a client SDK for version bumps, breaking method changes and examples.
Review command-line changes for renamed flags, changed exit codes and output format breaks.
Check that a new feature has metrics and alerts that would show it failing.
Check that a risky change has a documented rollback path.
Review changes to a state machine for missing transitions and impossible states.
Review generated code for hand edits that would be lost on regeneration.
Check copied or vendored code for licence compatibility and attribution.