Consider adding `danger` to repo for hygiene

example config:

import { danger, markdown, message, warn } from 'danger'

// Other ideas:
//  - verify TODO have work items linked

/* Keep Lockfile up to date  */
// TODO: CI job to run `yarn install` and confirm no changes
const packageChanged = danger.git.modified_files.includes('package.json')
const lockfileChanged = danger.git.modified_files.includes('yarn.lock')
if (packageChanged && !lockfileChanged) {
  const msg = 'Changes were made to package.json, but not to yarn.lock'
  const idea = 'Perhaps you need to run `yarn install`?'
  warn(`${msg} - <i>${idea}</i>`)
}

// More tests
const modifiedAppFiles = danger.git.modified_files.filter(
  (f) =>
    f.includes('src/') &&
    (f.endsWith('.ts') || f.endsWith('.js') || f.endsWith('.tsx') || f.endsWith('.jsx'))
)
/* Encourage more testing */
const hasAppChanges = modifiedAppFiles.length > 0
const testChanges = modifiedAppFiles.filter((filepath) => filepath.includes('.test.'))
const hasTestChanges = testChanges.length > 0

// Warn if there are library changes, but not tests
if (hasAppChanges && !hasTestChanges) {
  warn(
    "There are ts changes, but not tests."
  )
}

// Warn when there is a big PR
const bigPRThreshold = 500
if (danger.github.pr.additions + danger.github.pr.deletions > bigPRThreshold) {
  warn(':exclamation: Big PR')
  markdown(
    '> Pull Request size seems relatively large. If PR contains multiple changes, split each into separate PR will helps faster, easier review.'
  )
}

// No PR is too small to warrant a paragraph or two of summary
if (danger.github.pr.body.length === 0) {
  warn('There is no PR description. Get faster and better reviews by explaining what changed.')
}

// Congratulate when code was deleted
if (danger.github.pr.additions < danger.github.pr.deletions) {
  message(
    `✂️ Thanks for removing  ${danger.github.pr.deletions - danger.github.pr.additions} lines!`
  )
}

Start by reviewing the repository's existing CI and pull-request workflow, then compare it with the example checks for package.json, yarn.lock, src files, tests, and pull-request size or descriptions. Done means the selected Danger checks run for pull requests and report the intended hygiene warnings without blocking unrelated work.