portal-changelog

Posts user-facing changelog summaries of deployed portal changes to Slack channels.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/jpmoya/claude-agents --skill portal-changelog-jpmoya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portal-changelog
Source: https://github.com/jpmoya/claude-agents/tree/main/skills/portal-changelog
Command: npx skills add https://github.com/jpmoya/claude-agents --skill portal-changelog-jpmoya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing and posting release announcements for internal portals is repetitive and easy to get wrong — wrong channel, wrong version, or announcing unshipped work. This Skill automates drafting and posting a plain-language changelog to the correct Slack channel for the quoting portal or ops portal. ## Core Features & Use Cases - Channel-aware posting: Routes updates to #quoting_portal or #ops_portal using the correct channel IDs, avoiding the known duplicate channel. - Git-based change gathering: Reads the last posted changelog from channel history, then collects only commits shipped after it via git log on origin/main. - User-facing filtering and writing: Skips tests, CI, and refactors; writes plain-language bullets ordered by user impact under a single header showing the latest deployed version. - Use Case: After merging several PRs to the quoting portal, run /portal-changelog quoting to post a rolled-up update announcing the new version and what changed for users. ## Quick Start Ask the assistant to run /portal-changelog quoting to post a summary of the latest shipped changes to the quoting portal's Slack channel.

Frequently Asked Questions about portal-changelog

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

FAQPage Schema
How do I post a changelog update to a Slack channel?

Invoke the skill with the portal name, such as /portal-changelog quoting or /portal-changelog ops. It reads the channel history, gathers commits shipped since the last post, and sends a formatted summary via the Slack MCP send message tool.

How does the skill decide which changes to announce?

It finds the latest changelog post in the channel history, then lists commits on origin/main after that point. It filters out tests, CI, refactors, and type fixes, keeping only user-facing changes like features, UI updates, and pricing changes.

Can it post to any Slack channel or DM?

No. It only posts to #quoting_portal (C0BFS1X1Z3N) or #ops_portal (C0AHAU7GAR4). It never posts to other channels or DMs, and explicitly avoids the duplicate #quoting-portal channel.

How is the deployed version number determined?

For the quoting portal, the version is 1.0.<commit count> from git rev-list --count origin/main, matching the sidebar footer. For the ops portal, it reads the version field from package.json on main, and confirms it is live before posting.

What happens if the ops portal docs were not updated?

For the ops portal, the skill checks whether a user-facing change also updated the matching docs/user-guide page. If the docs were not updated, it flags the issue to JP instead of silently posting the changelog.