steward-changelog

Monitor a changelog channel to surface steward outcomes and advance cursors.

3|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/netguy204/vibe-engineer --skill steward-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steward-changelog
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/steward-changelog
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill steward-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Watches a project's changelog channel to surface steward outcomes and close the loop after a steward responds.

Core Features & Use Cases

  • Monitor the changelog channel and display steward updates.
  • Maintain a per-channel cursor stored locally to resume where you left off.
  • Acknowledge processed updates to advance the watch position and optionally continue watching.

Quick Start

Run ve board watch <changelog_channel> to start monitoring the changelog.

Frequently Asked Questions about steward-changelog

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

FAQPage Schema
How do I monitor a project changelog channel for steward updates?

You can monitor a project changelog channel by running ve board watch on the target channel to surface steward outcomes, which requires ve board watch capabilities and local cursor storage to resume where you left off.

What is the best way to track changelog updates across project management workflows?

Tracking changelog updates across project management workflows is best handled by watching the steward's changelog channel to surface outcomes, using a locally stored cursor per channel to resume monitoring seamlessly.

How do I acknowledge processed changelog updates to advance my watch position?

You acknowledge processed changelog updates by marking surfaced steward outcomes as processed, which advances the locally stored per-channel cursor and optionally continues watching the channel for new messages.

Do I need a server configuration to watch changelog updates locally?

A server configuration is not required to watch changelog updates locally because local cursor storage maintains your watch position; the server configuration is optional, used to display messages and advance cursors.

Why does my changelog watch position reset instead of resuming where I left off?

Your changelog watch position resets when the per-channel cursor stored locally is missing or not acknowledged, preventing the watch from resuming where you left off in the steward outcomes channel.