Software quality is not a one-time cleanup project; it is a habit that needs feedback, visibility, and guardrails. In this session, we will explore how GitHub Code Quality helps teams understand the health of their existing repositories, prioritize reliability and maintainability issues, and turn findings into actionable fixes with CodeQL-powered analysis and Copilot-assisted remediation. We will start by looking backward: using repository scans and dashboards to assess the current state of a codebase, identify high-impact issues, and create a practical path for improving code health without stopping delivery. Then we will shift to prevention: bringing Code Quality into pull requests so teams can catch problems before they reach the default branch, use clear findings during review, surface coverage signals, and apply rulesets that enforce quality standards as part of the development workflow. We will also look at how GitHub Copilot code review can support this process by reviewing pull requests, identifying issues from multiple angles, and suggesting fixes that developers can apply quickly while still validating the feedback through human review. Attendees will leave with a concrete approach for reducing existing technical debt while preventing new debt from entering their repositories, using GitHub Code Quality and GitHub Copilot code review as complementary tools for healthier, more maintainable software development.