Golang Stretchr Testify

[
  {
    "id": 1,
    "name": "assert-vs-require-precondition",
    "description": "Tests whether the model uses require for preconditions and assert for verifications, not mixing them randomly",
    "prompt": "Write a Go test using testify that parses a JSON config file, checks it has no error, verifies the config is not nil, then checks that config.Port equals 8080, config.Host equals 'localhost', and config.Debug is false.",
    "trap": "Model may use assert for the error check and nil check (preconditions), which would cause a nil pointer panic on subsequent assertions if parsing fails",
    "assertions": [
      {"id": "1.1", "text": "Uses require (not assert) for the NoError check on parsing"},
      {"id": "1.2", "text": "Uses require (not assert) for the NotNil check on config"},
      {"id": "1.3", "text": "Uses assert for the subsequent value checks (Port, Host, Debug)"},
      {"id": "1.4", "text": "Does NOT use require for all assertions indiscriminately"},
      {"id": "1.5", "text": "Argument order is (expected, actual) not (actual, expected) for Equal calls"}
    ]
  },
  {
    "id": 2,
    "name": "assert-new-naming-convention",
    "description": "Tests the skill's specific naming convention: 'is' for assert.New(t) and 'must' for require.New(t)",
    "prompt": "I'm writing Go tests with testify and I find the repeated 't' parameter verbose. How can I make my assertions more readable? Show me an example with both assert and require.",
    "trap": "Model may use generic variable names like 'a' and 'r', or 'assertions' and 'requirements' instead of the skill's recommended 'is' and 'must' convention",
    "assertions": [
      {"id": "2.1", "text": "Uses assert.New(t) to create a reusable assertion object"},
      {"id": "2.2", "text": "Uses require.New(t) to create a reusable require object"},
      {"id": "2.3", "text": "Names the assert.New(t) variable 'is'"},
      {"id": "2.4", "text": "Names the require.New(t) variable 'must'"},
      {"id": "2.5", "text": "Shows the 'is' and 'must' variables being used for different purposes (preconditions vs verifications)"}
    ]
  },
  {
    "id": 3,
    "name": "error-chain-assertion",
    "description": "Tests knowledge that is.Equal(ErrNotFound, err) fails on wrapped errors and ErrorIs should be used instead",
    "prompt": "I have a Go function that returns wrapped errors using fmt.Errorf with %w. Write a test that checks whether the returned error is ErrNotFound. The function signature is: func FindUser(id string) (*User, error)",
    "trap": "Model may use assert.Equal(ErrNotFound, err) which fails on wrapped errors instead of assert.ErrorIs",
    "assertions": [
      {"id": "3.1", "text": "Uses ErrorIs (not Equal) to check the error against ErrNotFound"},
      {"id": "3.2", "text": "Does NOT use assert.Equal or is.Equal to compare errors directly"},
      {"id": "3.3", "text": "Uses require for the initial error existence check if subsequent assertions depend on it"},
      {"id": "3.4", "text": "Argument order for ErrorIs is (err, target) not (target, err)"}
    ]
  },
  {
    "id": 4,
    "name": "mock-assert-expectations",
    "description": "Tests whether AssertExpectations is called — without it, mock expectations silently pass",
    "prompt": "Create a Go test using testify/mock for a NotificationService that calls a Sender.Send method. The test should verify that Send is called exactly once with the right email address.",
    "trap": "Model may set up On().Return() expectations but forget to call AssertExpectations(t), making the test pass even if Send is never called",
    "assertions": [
      {"id": "4.1", "text": "Mock embeds mock.Mock"},
      {"id": "4.2", "text": "Mock method uses m.Called() to forward arguments"},
      {"id": "4.3", "text": "Test calls m.AssertExpectations(t) to verify all expectations were met"},
      {"id": "4.4", "text": "Uses .Once() or equivalent call modifier to enforce exactly one call"},
      {"id": "4.5", "text": "Use