cs-end

Automates CS session closing and plugin version-up by coordinating 4 agents and pushing results to GitHub.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/intenet1001-commits/CSnCOMPANY --skill cs-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs-end
Source: https://github.com/intenet1001-commits/CSnCOMPANY/tree/main/plugins/cs-experiencing-v4/skills/cs-end
Command: npx skills add https://github.com/intenet1001-commits/CSnCOMPANY --skill cs-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end CS session closing and plugin version-up workflow within CSnCOMPANY's Claude Code ecosystem, streamlining analysis, learning storage, and GitHub updates.

Core Features & Use Cases

  • Parallel 4-Agent analysis in a single session to analyze changes, capture learnings, and prepare version bumps.
  • Automated documentation updates for CLAUDE.md, README.md, and marketplace.json based on session results.
  • Automated plugin version-up by updating VERSION files and plugin.json version fields.
  • Optional: seamless GitHub push of updates after versioning.

Quick Start

Invoke /cs-end to automatically close the current CS session and upgrade plugin versions.

Frequently Asked Questions about cs-end

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

FAQPage Schema
How do I automate Claude Code plugin versioning and session wrap-up?

Automating Claude Code plugin versioning and session wrap-up involves coordinating parallel agents to analyze changes, capture learnings, bump plugin versions, and push updates to GitHub. This Skill triggers that workflow using the /cs-end command.

What is the best way to update marketplace.json and plugin versions after a CI-CD session?

Updating marketplace.json and plugin versions after a CI-CD session is handled by parallel agents that automatically modify VERSION files, plugin.json version fields, and documentation based on session results before optionally pushing to Git.

Does cs-end require GitHub repository access to perform automated document updates?

Yes, cs-end requires GitHub repository access and configured agent prompts to perform automated document updates, version bumps, and Git operations within the Claude Code plugin workflow.

Can I use this to update CLAUDE.md and README.md documentation in parallel?

Yes, you can use this to update CLAUDE.md and README.md documentation in parallel, as the workflow coordinates four agents simultaneously to analyze changes and apply document updates alongside version bumps.

How does parallel agent coordination work for plugin version bumps?

Parallel agent coordination for plugin version bumps works by running four agents simultaneously to analyze session changes, store learnings, prepare version increments, and push automated Git updates for the Claude Code ecosystem.