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

How to fail pull requests that repeat storyboard effects with Saas Motion Kit

Set up the variety audit GitHub Action so every storyboard is checked on push and pull request.

  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA team that keeps promo storyboards in a shared repo and wants repeats caught before review.

The problemReviewers often miss repeated transitions or uncredited references when a storyboard changes over several commits.

The outcomeA check that runs on each push and pull request and fails when a storyboard repeats itself or a ref: has no credited row.

What you need first

  • Python to run the tools in tools/
  • A copy of the repo, or a new repo created from the template with Use this template
  • A storyboard file written from templates/STORYBOARD.md
  • HyperFrames, if you build the film itself (the README links to it but does not describe the install steps)
  • Claude Code, if you want the /saas-motion-video skill to run the process with you

Steps

  1. Create a repo from the template by clicking Use this template, or copy .github/workflows/variety-audit.yml into your repo.
  2. Keep each storyboard as STORYBOARD.md in the repo, with REFERENCES.md next to it if you cite references.
  3. Push a branch or open a pull request.
  4. Open the Actions tab and read the variety audit result.
  5. Fix each repeat or missing credit, then push again.

Prompt for your agent

Use the saas-motion-kit repo's variety-audit.yml workflow in <team repo>. Push a storyboard change to a branch and open a pull request. Expected output: a passing or failing variety audit check. Verify that the check fails on a storyboard that repeats an effect, and passes once it is fixed.

Caveat. The Action checks every STORYBOARD.md in the repo, so storyboards that are still drafts will fail until they are fixed or moved out of the checked path.

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