pop-routine-optimized

Cache git status and tests to reduce token usage in routine runs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Token-optimized morning/nightly routine execution by applying caching and selective tool calls to dramatically reduce token usage while preserving outcomes.

Core Features & Use Cases

  • Caching: skip unchanged checks (git status, tests) to avoid re-computation
  • Selective execution: only run tests or type checks when inputs change
  • Compact flags and summarization: apply --short/--quiet and condense outputs for efficiency
  • Use Case: running /popkit:routine morning --optimized on large projects to minimize token consumption while maintaining results

Quick Start

Run the optimized routine with /popkit:routine morning --optimized to begin token-efficient execution.

Frequently Asked Questions about pop-routine-optimized

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

FAQPage Schema
How do I reduce token usage when running pytest test and type check routines?

Reduce token usage in pytest routines by applying caching for git status and test results, selectively executing checks only when inputs change, and using compact command flags to condense outputs.

What is routine token optimization and how does caching preserve test outcomes?

Routine token optimization minimizes cost by caching git status and test results, skipping unchanged checks to avoid re-computation while preserving identical outcomes and maintaining determinism.

How do I run an optimized morning routine with caching enabled?

Run an optimized morning routine by executing /popkit:routine morning --optimized, which activates caching and selective tool calls to achieve token-efficient execution on large projects.

Can I use selective test execution and caching for large project automation workflows?

Yes, selective test execution and caching are designed for large project automation workflows, skipping unchanged checks and running type checks only when inputs change to minimize token consumption.

What is the best way to condense routine command outputs for token efficiency?

The best way to condense routine outputs is applying compact command flags like --short or --quiet and summarizing results, which dramatically reduces token usage while maintaining reliability.

Why does skipping unchanged git status checks save tokens without losing reliability?

Skipping unchanged git status checks saves tokens by avoiding redundant re-computation through caching, while selective execution ensures tests and type checks still run when inputs change, preserving reliability.