Close Epic (Ritual de Consolidación y Versionado)

Close software development Epics with security audits, CHANGELOG consolidation, and Git tagging.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gonzoblasco/club-camping-lobos --skill close-epic-ritual-de-consolidaci-n-y-versionado
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Close Epic (Ritual de Consolidación y Versionado)
Source: https://github.com/gonzoblasco/club-camping-lobos/tree/main/.agents/skills/close-epic
Command: npx skills add https://github.com/gonzoblasco/club-camping-lobos --skill close-epic-ritual-de-consolidaci-n-y-versionado

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures the formal closure of a development Epic with a structured process, including security audits, version control, and knowledge preservation.

Core Features & Use Cases

  • Security Audit Coordination: Invokes a sub-skill for a comprehensive security scan of the Epic's endpoints and changes.
  • Version Control: Finalizes a CHANGELOG, merges to the main branch, and creates a permanent tag in Git.
  • Knowledge Preservation: Documents the Epic's closure with lessons learned and preserves branches for historical reference.
  • Use Case: Perfect for software development teams looking to streamline the process of closing off a completed Epic while maintaining code integrity and security.

Quick Start

Use the Close Epic skill to initiate the closure of Epic E[5] - "New Feature Implementation".

Frequently Asked Questions about Close Epic (Ritual de Consolidación y Versionado)

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

FAQPage Schema
How do I close a development epic with a security audit and Git version control?

Closing a development epic requires a structured process that coordinates a security scan of endpoints, consolidates the CHANGELOG, merges branches, and creates a permanent Git tag to preserve code integrity.

What is the best way to consolidate a CHANGELOG and preserve branches when finalizing an epic?

The best way to finalize an epic involves documenting lessons learned, consolidating the CHANGELOG, and preserving historical branches in Git to maintain a permanent record of the development workflow.

Can I run a security scan on endpoint changes during the epic closure workflow?

Yes, the epic closure workflow invokes a comprehensive security scan of the epic's endpoints and changes, coordinating with security tools to ensure no vulnerabilities are merged into the main branch.

Does epic closure require additional tools for security scanning and Git operations?

Epic closure requires Git operations for branch merging and tag creation, and it may use additional external tools to perform comprehensive security scanning of the finalized code changes before version control consolidation.

When should I not use an automated epic closure process for my software development workflow?

You should avoid automated epic closure if your software development workflow lacks finalized Git branches or if the required security audit and CHANGELOG consolidation steps have not been completed beforehand.

Why does formal epic closure include creating a permanent tag in Git?

Formal epic closure creates a permanent Git tag to establish an immutable historical reference point in version control, ensuring the finalized code state and security audit results are permanently preserved.