# Refresh Repos

> Pull the latest changes for cloned M-KOPA repos, optionally filtered by keyword. Use when the user wants to refresh, pull, or update local repos before investigating something, or asks whether local code is current. Triggers on "refresh repos", "pull latest", "update the repos", "is my local code current".

- Skill: `mk-joshuajallen/refresh-repos` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mk-joshuajallen/refresh-repos`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mk-joshuajallen/refresh-repos/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mk-joshuajallen (https://skillmd.com/u/mk-joshuajallen)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/mk-joshuajallen/refresh-repos

---


# Refresh Repos

Pull the latest changes for cloned M-KOPA repos at `~/Repos/`.

## Usage

- `/refresh-repos` — pull all cloned repos
- `/refresh-repos corelending` — pull only repos matching a keyword (case-insensitive)

## Instructions

1. Check for a filter keyword in the arguments.
2. List directories in `~/Repos/`, filtered by the keyword if given.
3. For each match, run `git -C <path> pull --ff-only` and capture the output.
4. Report concisely:
   - **Updated** — repos with new commits, showing git's summary line
   - **Already current** — a single count, never a list
   - **Errors** — the repo and the error
5. Keep it short. Do not repeat "Already up to date." per repo.
6. If anything was pulled, say so clearly — the user needs to know something changed underneath them.

## Note on freshness

If repos were updated and the session has already made claims based on the previous state, flag which claims may now be stale.