morning

Compute a Ready to Code Score from STATUS.json and tooling data.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jrc1883/popkit-ai --skill morning-jrc1883
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: morning
Source: https://github.com/jrc1883/popkit-ai/tree/main/packages/popkit-dev/skills/pop-morning
Command: npx skills add https://github.com/jrc1883/popkit-ai --skill morning-jrc1883

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires popkit-shared, and includes scripts (resource) components.

What problem does it solve?

Automated morning readiness checks that restore session context and validate dev environment so you can start coding with confidence.

Core Features & Use Cases

  • Calculates a Ready to Code Score (0-100) across session restoration, service health, dependency freshness, branch sync, PR reviews, and issue triage.
  • Automatically captures session state to STATUS.json to preserve work state between sessions.
  • Triggered by /popkit:routine morning to provide a clear status report and actionable next steps.

Quick Start

Run the morning routine to restore your session and obtain the Ready to Code Score.

Frequently Asked Questions about morning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my dev environment is ready to code after a morning startup?

A Ready to Code Score evaluates session restoration, service health, dependency freshness, branch sync, PR reviews, and issue triage to produce a 0-100 numeric rating with a structured markdown breakdown of your workstation status.

What is a Ready to Code Score and how does it assess developer workstation status?

A Ready to Code Score evaluates session restoration, service health, dependency freshness, branch sync, PR reviews, and issue triage to produce a 0-100 numeric rating with a structured markdown breakdown of your workstation status.

How do I calculate a developer readiness score using STATUS.json and git tools?

You calculate developer readiness by feeding state data from STATUS.json into the morning routine, which optionally integrates git, gh, and pnpm tooling outputs to assess session state and service health gracefully.

Does the morning readiness routine require specific dependencies like pnpm or gh to run?

The morning readiness routine does not require specific dependencies; it accepts optional tooling like git, gh, and pnpm to enhance analysis but handles missing data gracefully to compute the readiness score.

Can I capture and restore my dev session state between coding sessions?

You can capture and restore dev session state between coding sessions by automatically writing workstation context to STATUS.json, which the morning routine reads to restore your previous work state.

What happens if STATUS.json or git tooling data is missing when calculating the readiness score?

If STATUS.json or tooling data is missing, the readiness score calculation handles the missing data gracefully, ensuring the morning routine still returns a numeric score and structured breakdown without failing.