session-close

Automate end-of-session code checks by running a structured checklist that executes static analysis, security audits, documentation updates, and CI/CD pipeline verification before finalizing a deployment.

A Git session close checklist should include running type checking, loading security audits, updating changelogs and architecture docs, committing changes, and verifying CI/CD pipelines before notifying the team.

Yes, running an automated session close requires repository access, Bash, Git, and CI/CD tooling to successfully execute static analysis, commit changes, and verify deployment pipelines.

Update documentation and manage Jira tickets by applying an end-of-session checklist that automatically refreshes changelogs, READMEs, architecture docs, and cleans up related tickets upon session completion.

The best way to commit changes and notify Slack is to use an automated session close process that commits Git updates, verifies CI/CD pipelines, and posts a final session summary to team channels.

Deployment verification fails without a structured checklist because static analysis, security audits, and documentation updates are often missed, leading to unverified code being committed to CI/CD pipelines.