summary

Generate HTML summaries of code diffs and documentation for PRs and releases.

14|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/brsbl/ottonomous --skill summary-brsbl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summary
Source: https://github.com/brsbl/ottonomous/tree/main/skills/summary
Command: npx skills add https://github.com/brsbl/ottonomous --skill summary-brsbl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires highlight.js, marked, marked-highlight, and includes scripts (resource) components.

What problem does it solve?

Developers often struggle to translate code changes into stakeholder-friendly narratives. This Skill converts diffs and documentation into a concise, publish-ready HTML summary that communicates rationale and impact.

Core Features & Use Cases

  • Generate semantic summaries from code changes and associated docs to accompany PRs and releases.
  • Produce change narratives suitable for release notes, changelogs, and executive summaries.
  • Provide a consistent, browsable HTML report that highlights changed files, components touched, and the reasoning behind changes.

Quick Start

Run the summary on your current branch to generate an HTML narrative of changes.

Frequently Asked Questions about summary

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

FAQPage Schema
How do I summarize code changes for pull requests and release notes?

You can generate a human-readable HTML summary from code diffs and documentation to produce concise PR notes, release narratives, and change logs highlighting changed files and components.

What is the best way to generate a change log from a feature branch diff?

The best way to generate a change log from a feature branch diff is to apply frontmatter-driven metadata extraction to render an easily navigable HTML report with syntax-highlighted code blocks and consistent formatting.

Can I create syntax-highlighted HTML documentation from code diffs?

Yes, you can create syntax-highlighted HTML documentation from code diffs by leveraging rendering libraries to produce a consistent, browsable report that highlights touched components and reasoning.

Does this approach work for generating executive summaries of software releases?

Yes, this approach works for generating executive summaries of software releases by converting code documentation and diffs into a concise, publish-ready HTML narrative that communicates impact and rationale.

Do I need markdown and syntax highlighting libraries to render code documentation summaries?

You need markdown parsing and syntax highlighting libraries to render code documentation summaries, applying frontmatter-driven metadata extraction to generate consistently formatted, browsable HTML reports.