skills.rest
danielstewart77
danielstewart77COMMUNITY
Explore all skills by this author →
GitHub

story-close

Deploy completed software stories by pulling code, rebuilding Docker containers, and updating Planka status.

1|Updated Mar 11, 2025
Search Tags:#automation#git#ci/cd#deployment#docker#planka
One-click install
npx skills add https://github.com/danielstewart77/hive_mind --skill story-close
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-close
Source: https://github.com/danielstewart77/hive_mind/tree/main/specs/skills/story-close
Command: npx skills add https://github.com/danielstewart77/hive_mind --skill story-close

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the final steps of deploying a completed software story to production after its associated pull request has been merged.

Core Features & Use Cases

  • Automated Deployment Workflow: Orchestrates pulling the latest code, rebuilding application containers, and performing a health check.
  • Task Management Integration: Updates the status of a story in Planka to 'Done' and adds a confirmation comment.
  • Notification System: Informs the owner about the successful deployment and verification.
  • Use Case: After merging a feature branch for a new user authentication flow, this Skill ensures the production environment is updated, stable, and the corresponding task is marked as complete.

Quick Start

Use the story-close skill to close out the story with card ID 12345.

Frequently Asked Questions about story-close

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

FAQPage Schema
How do I automate Docker deployment after merging a pull request?▼

Automate Docker deployment by pulling the latest master branch code, rebuilding containers, and performing a health check to verify production stability before updating task status.

Can I update Planka task status to Done automatically after a deployment?▼

Yes, Planka task status updates automatically to Done after deployment. The workflow requires a Planka card ID as input to identify the specific story and adds a confirmation comment upon completion.

How does automated CI/CD story closure work with Git and Docker Compose?▼

Automated story closure works by pulling the latest Git code, rebuilding Docker Compose containers, running a health check, updating the task tracker, and sending an owner notification upon success.

Do I need a specific card ID to deploy completed stories to production?▼

Yes, a Planka card ID is required as input to identify which completed story to deploy, allowing the system to update the correct task status and notify the appropriate owner.

What is the best way to notify an owner after a production deployment succeeds?▼

Notify an owner after deployment by integrating a notification service that triggers automatically once the Docker rebuild and health check verify the production environment is stable and updated.

When should I not use an automated deployment workflow for completed stories?▼

Avoid automated deployment when a pull request has not been merged into the master branch, as the workflow depends on pulling the latest merged code to rebuild and verify Docker containers.

Related Skills

Explore More Software Engineering Skills→
nashgaonashgao
3

Merge Pull Request Command

Merge pull requests into a target branch with validation and quality gates.

Community
Advanced
danielstewart77danielstewart77
1

story-start

Fetch a Planka card, create a project directory, and generate an implementation plan.

Community
Advanced
sumik5sumik5
2

managing-docker

Manage Docker container lifecycles, images, and Compose projects.

Community
Intermediate
bomberoxenviosdosruedasbomberoxenviosdosruedas

agency-devops-automator

Automate DevOps workflows with Terraform, GitHub Actions, Kubernetes, and Prometheus.

Community
Advanced