How do I install the Build Capture skill?

Run npx skillmds@latest add naticorrea-03/build-capture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Build Capture safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build Capture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build Capture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Build Capture?

naticorrea-03 (@naticorrea-03) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build Capture by naticorrea-03 — Agent Skill

Name: Build Capture
Author: naticorrea-03

Build Capture

A hands-off daily log of everything you build in Claude Code. Once a day it reads that day's sessions and the files that changed, and appends a short entry per real build (what it is, what shipped) to a local markdown file. No /wrap, no manual step. Perfect for standups, changelogs, or a running record of what you've made.

naticorrea-03 1e53fa0 5 files · 9.7 KB Updated Sep 17, 2026

File contents

build-capture

The stuff you build in Claude Code never gets written down unless you stop and do it. You won't. This does it for you.

Once a day a cron reads that day's Claude Code sessions plus the files that changed in a folder you watch, figures out what you actually built or shipped, and appends a short entry for each to a markdown file. Hands-off. Routine chatter and pure Q&A are skipped.

What you get, per build

Name — short title of the thing you built
What it is — one plain sentence
Latest — what happened today (built, shipped, fixed, refactored)
Type (skill / script / app / fix) + date

Setup (2 minutes)

Requires the claude CLI on your PATH and Python 3.
Set WATCH_DIR to the folder you build in (default: the current repo / ~/.claude/skills), and LOG_FILE for the log (default ~/build-log.md).

Install the daily cron:

cp com.example.build-capture-daily.plist ~/Library/LaunchAgents/
# edit the path inside to point at this folder, then:
launchctl load ~/Library/LaunchAgents/com.example.build-capture-daily.plist

(On Linux, use the crontab line in daily-sweep.sh's header.)

Run it by hand

./daily-sweep.sh          # log today's builds now
./daily-sweep.sh dry      # print what it would log, write nothing

How it works

build_digest.py (pure local, no LLM) collects the last day's session text, the files that changed under WATCH_DIR, and recent git commits, into one digest. A headless claude pass reads it per SWEEP_PROMPT.md and appends the builds to your log, deduping by name so re-runs don't pile up. Additive only, it never edits past entries.

---name: build-capturedescription: A hands-off daily log of everything you build in Claude Code. Once a day it reads that day's sessions and the files that changed, and appends a short entry per real build (what it is, what shipped) to a local markdown file. No /wrap, no manual step. Perfect for standups, changelogs, or a running record of what you've made.---# build-captureThe stuff you build in Claude Code never gets written down unless you stop and do it. You won't. This does it for you.Once a day a cron reads that day's Claude Code sessions plus the files that changed in a folder you watch, figures out what you actually built or shipped, and appends a short entry for each to a markdown file. Hands-off. Routine chatter and pure Q&A are skipped.## What you get, per build- **Name** — short title of the thing you built- **What it is** — one plain sentence- **Latest** — what happened today (built, shipped, fixed, refactored)- Type (skill / script / app / fix) + date## Setup (2 minutes)1. Requires the `claude` CLI on your PATH and Python 3.2. Set `WATCH_DIR` to the folder you build in (default: the current repo / `~/.claude/skills`), and `LOG_FILE` for the log (default `~/build-log.md`).3. Install the daily cron: ``` cp com.example.build-capture-daily.plist ~/Library/LaunchAgents/ # edit the path inside to point at this folder, then: launchctl load ~/Library/LaunchAgents/com.example.build-capture-daily.plist ``` (On Linux, use the `crontab` line in `daily-sweep.sh`'s header.)## Run it by hand```./daily-sweep.sh # log today's builds now./daily-sweep.sh dry # print what it would log, write nothing```## How it works`build_digest.py` (pure local, no LLM) collects the last day's session text, the files that changed under `WATCH_DIR`, and recent git commits, into one digest. A headless `claude` pass reads it per `SWEEP_PROMPT.md` and appends the builds to your log, deduping by name so re-runs don't pile up. Additive only, it never edits past entries.

Frequently asked questions