magnus-publish

Publish website changes to GitHub via a validated feature-branch pull request.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ssu96ld/magnus-claude-plugins --skill magnus-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magnus-publish
Source: https://github.com/ssu96ld/magnus-claude-plugins/tree/main/plugins/magnus-site/skills/magnus-publish
Command: npx skills add https://github.com/ssu96ld/magnus-claude-plugins --skill magnus-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability automates the end-to-end publishing workflow for the Magnus Consulting website. It validates the local magnus repository, builds the site, commits changes to a feature branch, pushes, and opens a pull request on GitHub, ensuring every change goes through PR review and is not pushed directly to main.

Core Features & Use Cases

  • Validates repository readiness: checks for package.json with astro in dependencies, src/pages, and docs/llm-context.md before publishing.
  • Pre-flight checks: runs npx astro check and npm run build, failing gracefully if errors are detected.
  • Branch management: creates a feature branch from main (or reuses an existing one) and guards against creating new PRs if a branch already has an open PR.
  • Atomic staging and committing: stages only touched files under src/pages, src/data, src/components, src/content, and updates docs/llm-context.md as needed, while refusing secrets or ignored files.
  • PR creation and audit embedding: pushes the branch, opens a PR with a commit message and embedded approvals from the .magnus-changes/pending.log, and ensures approvals accompany the PR.
  • Audit log management: truncates the pending log after PR creation.
  • Scope limitation: not intended for editing/creating content; use magnus-edit-* or magnus-add-* skills for content changes.

Quick Start

Run magnus-publish after all changes are ready and approved to publish them via a feature-branch PR workflow.

Frequently Asked Questions about magnus-publish

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

FAQPage Schema
How do I publish Astro website changes to GitHub via a pull request workflow?

Website changes are published by validating the Astro repository, building the site, staging touched files into a feature branch, and opening a GitHub PR with an embedded audit trail from the pending log.

What pre-flight checks are required before deploying a feature branch with Astro?

Pre-flight checks run npx astro check and npm run build to validate the site before pushing a feature branch, failing gracefully if errors are detected to prevent broken deployments.

Does the PR-driven deploy workflow enforce main branch protection?

The PR-driven deploy workflow enforces main branch protection by committing changes to a feature branch and refusing to push directly to main, ensuring all changes go through PR review.

How does the CI-CD pipeline handle the audit log when opening a pull request?

The pipeline reads .magnus-changes/pending.log to compose the commit message and PR body, embedding approvals in the pull request and truncating the pending log after PR creation.

What files are staged during an atomic commit for a web deploy?

During an atomic commit, the workflow stages only touched files under src/pages, src/data, src/components, and src/content, while updating docs/llm-context.md and refusing secrets or ignored files.

Can I edit website content directly while using the publish workflow?

The publish workflow is not intended for editing content; it is scoped only for publishing. You should use magnus-edit or magnus-add skills for content changes before deploying.