DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to gate a build or pipeline on fresh video sidecars with Cdaf

Use Cdaf validate as an exit-code check so stale descriptions never reach downstream steps.

Who it is forA DevOps or CI engineer whose pipeline feeds video files to AI agents and needs to reject outdated descriptions.

The problemA video edited after its description was written can silently feed wrong content to downstream agents.

The outcomeThe pipeline stops on any video whose sidecar is missing or stale, and continues only when all sidecars are fresh.

What you need first

  • Python 3.10 or newer
  • Node.js with npx for the agent skill install
  • A Gemini API key (bring your own) for generating sidecars, or the local provider for no-key generation
  • ffmpeg, only if you run the synthetic benchmark

Steps

  1. Run pip install "cdaf[generate] @ git+https://github.com/UditAkhourii/cdaf.git#subdirectory=cli" on the build runner, or install the CLI from a clone with pip install ./cli[generate].
  2. Run cdaf validate ./footage/clip.mp4 for each video in the pipeline.
  3. Fail the job when the command exits with a nonzero code, and regenerate with cdaf generate ./footage for any stale clip.
  4. Run cdaf read ./footage/clip.mp4 in downstream steps to get the description after the hash check passes. (inferred, check the README)

Prompt for your agent

Using the CDAF CLI from the repo UditAkhourii/cdaf, run `cdaf validate` on each video path in <video-list> and report the exit code for each. Stop and list any video whose sidecar is missing or stale, and verify that validate exits 0 for every video that passes.

Caveat. The validate and read commands need no API key, but sidecars must already exist, so generation still needs a Gemini key or the local provider.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page