seal

Draft commit messages and archive plans from active plan files.

Updated May 5, 2026
One-click install
npx skills add https://github.com/NaNathan13/cool-fse-claude-workflow --skill seal-nanathan13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seal
Source: https://github.com/NaNathan13/cool-fse-claude-workflow/tree/main/kit/.claude/skills/seal
Command: npx skills add https://github.com/NaNathan13/cool-fse-claude-workflow --skill seal-nanathan13

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of drafting commit messages, marking plans as completed, and organizing workflow documentation, simplifying the finalization phase of project tasks.

Core Features & Use Cases

  • Drafts commit messages based on plan details and diff analysis.
  • Marks the current plan as done and moves it to the done directory.
  • Use Case: For a developer finalizing a feature, this Skill helps generate a meaningful commit message and properly archive the plan, ensuring organized project history and reducing manual effort.

Quick Start

Use the seal skill to analyze the current plan, create a commit message, and archive the plan into the completed folder.

Frequently Asked Questions about seal

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

FAQPage Schema
How do I automate drafting git commit messages from project plans?

Automating git commit messages involves analyzing your current plan details and code diffs to generate a meaningful commit summary. This Skill drafts the message and marks the corresponding plan as completed for organized project history.

What is the best way to archive completed workflow plans in a git project?

Archiving completed workflow plans requires moving active plan files from the `.claude/plans/active/` directory into a done directory. This Skill finalizes your task by marking the plan as done and organizing your workflow documentation automatically.

Do I need existing plan files to automate my commit finalization workflow?

Yes, automating commit finalization requires existing plan files located in `.claude/plans/active/` and access to git commands. The Skill uses these structured planning files to analyze changes and generate accurate commit messages.

How does diff analysis work when finalizing a feature commit?

Diff analysis for finalizing a feature commit works by evaluating your staged code changes alongside your active plan details. This Skill uses that analysis to draft a context-aware commit message before archiving the plan.

Can I use this Skill for project management tasks outside of git workflows?

No, this Skill applies primarily to developers managing Git-based projects with structured planning and review processes. It specifically finalizes tasks by generating commit messages and archiving plans within Git-based project workflows.

Why does my plan archiving process require moving files to a done directory?

Moving files to a done directory organizes workflow documentation and ensures a clean project history. This Skill marks your current plan as done and moves it to the completed folder to finalize the task and reduce manual effort.