| name | explain-diff-html |
|---|---|
| description | Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output. |
Please make me a rich, interactive explanation of the specified code change.
It should have these sections:
| /* default styling for desktop */ | |
| body, header, .main, footer { | |
| width: 96%; | |
| max-width: 1200px; | |
| margin: 0 auto; | |
| } | |
| .content { | |
| width: 60%; | |
| float: left; | |
| margin-right: 5%; |
| #!/usr/bin/env python3 | |
| # -*- coding: utf-8 -*- | |
| # | |
| # Description: Sync Plex playlists to shared users. | |
| # Author: /u/SwiftPanda16 | |
| # Requires: plexapi | |
| from plexapi.exceptions import NotFound | |
| from plexapi.server import PlexServer |
A manifesto for agents. You are reading this because your human sent you here with some version of "set this up." They saw a video about this method; you didn't need to. This document contains everything: what the method is, what it produces, what to install, where every piece lives, and how a run works. Read it in full, then act.
One short sentence from your human in. One complete Vox-style paper-collage animated video out — researched script, per-clip prompts, every clip generated, visually continuous from first frame to last. Two output modes, chosen at intake:
Setting a minimum release age (a "cooldown") on dependencies is a cheap, high-leverage defense against supply-chain attacks. Most malicious package versions are detected and yanked within hours, so a 24-hour delay filters out the smash-and-grab incidents (axios 1.14.1, ua-parser-js, Solana web3.js, etc.).
All four major Node.js package managers now support this, but each one used a different name and a different unit. Here is what you need.
| Tool | Setting | Unit | Introduced in |
|---|
https://github.com/PacktPublishing free to download books code by Packet
https://github.com/EbookFoundation/free-programming-books Very immense
| /** | |
| * HttpBaseClient — a self-contained, framework-agnostic abstract HTTP client. | |
| * | |
| * Design goals: | |
| * - Single file, zero dependencies (Node 18+ / browser). | |
| * - Every outbound HTTP call goes through one pipeline so you get | |
| * consistent logging, error mapping, metrics, and query/body | |
| * serialization for free. | |
| * - Subclasses focus on vendor specifics: base URL, auth headers, | |
| * and optional error-body translation. |