skills.rest
Noetfield-Systems
Noetfield-SystemsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

hub-pro-change-log

Appends structured change log entries to a shared JSON experience log after app builds and fixes.

Updated Jun 20, 2026
Search Tags:#cli#multi-agent#knowledge sharing#change log#append#json log#app experience
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill hub-pro-change-log-noetfield-systems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hub-pro-change-log
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/hub-pro-change-log
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill hub-pro-change-log-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple agents ship app changes, knowledge about obstacles, fixes, and lessons learned gets lost between sessions. This Skill enforces a mandatory append-only change log so every agent can read what previous agents shipped, what blocked them, and what golden tips they left behind. ## Core Features & Use Cases - Structured log appends: Record app_id, agent, summary, obstacles, fixes, golden tips, and touched paths into a shared JSON log via a single CLI command. - Read-before-edit queries: List all logged apps or fetch the full history for a specific app before making changes. - UI ledger integration: Optionally append a parallel UI upgrade ledger entry when a change modifies the interface. - Use Case: After fixing an e2e failure in the mac_health app, an agent appends an entry describing the blocker and fix, so the next agent working on mac_health sees the context immediately. ## Quick Start Append a change log entry for the app you just modified by running the hub_pro_skills_v1.py script with your agent id, summary, obstacles, and fixes.

Frequently Asked Questions about hub-pro-change-log

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

FAQPage Schema
How do I append a change log entry after an app fix?▼

Run python3 scripts/hub_pro_skills_v1.py with the --append flag, passing --app, --agent, --summary, and optionally --obstacles, --fixes, --paths, and --json. The entry is written to data/hub-pro-app-experience-log-v1.json.

How do I read the change history for a specific app before editing?▼

Run python3 scripts/hub_pro_skills_v1.py --app mac_health --json to fetch all entries for that app, or use --list-apps --json to see every app that has logged entries.

When should I append an entry to the app experience log?▼

Append after every change that ships to disk: UI upgrades, API route changes, .app rebuilds, e2e fixes, and incident resolutions. Chat-only completion claims without a log entry are explicitly disallowed.

What fields are required in a change log entry?▼

app_id, agent, and summary are required. Obstacles, fixes, golden_tips, and paths are recommended so future agents understand what blocked the work and how it was resolved.

What should not go into the shared experience log?▼

Do not log secrets, duplicate entries without new facts, or chat-only done claims without an actual entry. Keep summaries to one founder-readable sentence.

Related Skills

Explore More Software Engineering Skills→
RCSnyderRCSnyder

build-discipline

Enforce small test-first vertical slices during BUILD and verify-fix cycles.

Community
Intermediate
gitwaltergitwalter

health-check

Analyze team health metrics and generate structured reports with recommendations.

Community
Advanced
aaronjmarsaaronjmars
626

Evening Recap

Generate end-of-day operational recaps from local activity logs and cron-state data.

Community
Advanced
gongye19gongye19

git-workflow

Enforce Git workflow best practices for commits, branches, and pull requests.

Community
Intermediate