It would be great to run static analysis tools on pull requests.

One that looks really good:
https://github.com/marketplace/actions/clang-tidy-review

• It only runs on changes in the pull request
• Adds comments inline to the PR code
• Can use compile_commands.json (-DCMAKE_EXPORT_COMPILE_COMMANDS=ON to cmake)

An example with similar Qt build process:
https://github.com/Mudlet/M

Is your feature request related to a problem? Please describe.
Occasionally I need to construct a NeighborList from bond topology data, which is currently somewhat hard to do. I've written the pattern below at least a dozen times, and it would be much better as a single function.

Describe the solution you'd like
A new class method like `NeighborList.from_system(system, indices, weight

doctests will actually run the code-blocks and ensure that you get the expected output. This should prevent documentation from going out of date or having silly typos.

We should make a pass (namely after the SQL change) to ensure status attributes are consistent throughout the code and all pull from one Enum pydantic model object if possible.

Summary of discussion with @utf and @scanlond based on user feedback.

• Users can get confusing/incorrect results when using kgen with a non-primitive POSCAR
• kgen warns that results may be incorrect and writes a POSCAR_prim file along with a KPOINTS which corresponds to that primitive/standard cell setting.
• If the user ignores this warning and uses their current POSCAR with this

A standard test suite for QC programs should be curated that run over several dimensions at a minimum:

• Driver: energy/gradient/Hessian
• Reference: UHF/RHF
• Relevant procedures: optimization

We needed this yesterday on models.Molecule. Posting it in case anyone wants a starter project. Should test on example that does and doesn't have fix_com set. (True should give origin.)