source-command-technical-update

Generates weekly Cinematic Canvas product update documents from git history with changelog maintenance and image prompts.

5|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/portalshq/portals-studio --skill source-command-technical-update-portalshq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-technical-update
Source: https://github.com/portalshq/portals-studio/tree/main/.agents/skills/source-command-technical-update
Command: npx skills add https://github.com/portalshq/portals-studio --skill source-command-technical-update-portalshq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, technically accurate weekly product updates requires manually reviewing git history, maintaining a changelog, drafting structured release notes, and producing visual assets. This Skill automates that entire editorial workflow for the Cinematic Canvas project. ## Core Features & Use Cases - Git-Driven Context Gathering: Pulls recent commits, reads the previous week's update for continuity, and maintains a deduplicated rolling 30-day CHANGELOG.md. - Structured Document Drafting: Produces a sub-1200-word update following a fixed template with frontmatter, feature sections, benefit statements, and a three-paragraph conclusion. - Visual Asset Generation: Defines prompts for one cinematic cover image and three technical graphics via the brand-aware-nanobanana skill, with a fail-safe that inserts placeholder paths if image generation fails. - Use Case: A maintainer runs the weekly update command to turn the past week's commits into a publishable blog post in website/content/updates/, complete with changelog sync, images, and a social media preview. ## Quick Start Run the technical-update command to generate this week's Cinematic Canvas product update from recent git history.

Frequently Asked Questions about source-command-technical-update

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

FAQPage Schema
How do I generate a weekly product update from git commits?

Run the technical-update command, which pulls recent git history, reads the previous update for continuity, drafts a structured Markdown document, and generates image prompts. The output is saved to website/content/updates/ and committed with the changelog.

How does the changelog maintenance work in this workflow?

The skill syncs impactful commits since the last update into CHANGELOG.md, skipping duplicates already present. Entries are kept in descending date order and pruned to a rolling 30-day window.

What happens if image generation fails during the update?

The fail-safe still inserts image markdown, captions, and expected file paths into the document as placeholders. The image prompts are returned to the user so assets can be generated later.

What document structure does the weekly update follow?

The update uses YAML frontmatter with title, author, date, description, and cover image, followed by feature sections with bolded spec labels, a What's Shipping Next list, and a mandatory three-paragraph conclusion ending with a fixed sign-off sentence.

What are the limitations of this update generation workflow?

It is specific to the Cinematic Canvas repository structure and depends on the brand-aware-nanobanana skill for images. Quantitative claims require real data from commits, and it does not invent metrics.