update

Regenerate research reports as v+1 versions via the FeedRadar CLI.

Updated May 10, 2026
One-click install
npx skills add https://github.com/ozzy-labs/feedradar --skill update-ozzy-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/ozzy-labs/feedradar/tree/main/src/claude-skills/update
Command: npx skills add https://github.com/ozzy-labs/feedradar --skill update-ozzy-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate an existing research report as a new v+1 version via the FeedRadar CLI, preserving immutable history by rewriting and superseding the predecessor without touching the original.

Core Features & Use Cases

  • Thin wrapper around the radar CLI that handles predecessor parsing, version increment, and the supersedes wiring, delegating the heavy lifting to the CLI and adapters.
  • Supports host-agent mode (opt-in) to emit a payload for manual review or to commit the v+1 document.
  • Enforces immutable history semantics for items.yaml by keeping the predecessor unchanged while presenting the new version to users.

Quick Start

Run radar update <id> to generate a v+1 research file that supersedes the predecessor while preserving immutable history.

Frequently Asked Questions about update

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

FAQPage Schema
How do I version-control a research report and preserve immutable history?

Version-control a research report by generating a new v+1 file that supersedes the predecessor. The original report remains untouched, preserving immutable history while the new version is presented for review.

What is the best way to supersede an existing research report without modifying the original file?

Supersede an existing research report by delegating to the FeedRadar CLI for predecessor parsing, version increment, and supersedes wiring. This process creates a new v+1 version while enforcing immutability for the original items.yaml status.

How do I generate a new report version using a CLI?

Generate a new report version by running the radar update command with the report ID. The CLI handles the heavy lifting, parses the predecessor, increments the version, and outputs the new v+1 file path and supersedes relationship.

Does the report versioning process support manual review before committing?

Report versioning supports an opt-in host-agent mode that emits a payload for manual review. This allows you to review the v+1 document before committing it, ensuring the new research report meets your standards.

Can I use this CLI update method to enforce status invariance across report versions?

The CLI update method enforces items.yaml status invariance across versions. It keeps the predecessor unchanged while wiring the supersedes relationship, ensuring consistent status tracking throughout the report lifecycle.