SDLC audit

Reads one repository and reports which stages of the lifecycle exist, which exist in part and which are missing. Agents write code fast. A product built that way breaks in the stages around the code: no ticket says what done means, no test runs before merge or deploy, nothing stops a bad deploy, nobody can roll back, and nobody sees the error before a user does. This audit names those gaps, ranked by what they cost for this repository's purpose.

It needs no other module. It reads files and runs read-only commands; it changes nothing. The probes run in probe.py, next to this file, so the same rules give the same states on every run.

Inputs

• Repository root (default: the current directory).
• Purpose: what the repository ships to. Ask if it is not clear from the README.
  • users: a service, a site or an app that people use.
  • grader: a one-shot submission, a take-home, a hackathon entry.
  • nothing: a sandbox, a spike, a personal experiment.
• Author: the user's commit email or name (default: git config user.email). History probes count only the user's commits; inherited history (a template, a fork, an organiser's starter repo) is reported apart.
• Remote: run git remote -v first. If origin belongs to another account or organisation, every GitHub probe is "not checked (upstream)". Issues, pull requests and branch protection of someone else's repository say nothing about this team.

Steps

1. Run the probe.