make-closed-issue

Name: make-closed-issue
Availability: InStock
Author: Bitsocial

Create a GitHub issue from recent changes and move it to Done.

1|1|Updated Feb 1, 2026

Search Tags:#automation #workflow #github #traceability #issue #project-board #commit-diffs

Ready to run

npx skills add https://github.com/bitsocialnet/bitsocial-web --skill make-closed-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: make-closed-issue
Source: https://github.com/bitsocialnet/bitsocial-web/tree/main/.cursor/skills/make-closed-issue
Command: npx skills add https://github.com/bitsocialnet/bitsocial-web --skill make-closed-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically creates a GitHub issue from recent changes, and ensures traceability by linking commits and updating project boards.

Core Features & Use Cases

Infer the scope of changes and generate a descriptive issue.
Commit only the relevant diffs with conventional messages.
Close the issue using the full commit hash and move it to the Bitsocialnet project board as Done.

Quick Start

Say 'make closed issue' after completing changes to automatically create a GitHub issue, commit only the relevant diffs, close the issue with the commit hash, and move it to the Bitsocialnet project board as Done.

Frequently Asked Questions about make-closed-issue

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

FAQPage Schema

How do I automatically close a GitHub issue from recent commits?▼

To automatically close a GitHub issue from recent commits, this workflow infers the scope of changes, generates a descriptive issue, commits relevant diffs with conventional messages, and closes the issue using the full commit hash. It then moves the issue to Done on the project board.

Can I update a GitHub project board to Done automatically after committing changes?▼

Yes, you can update a GitHub project board to Done automatically. After generating an issue and committing the relevant diffs, the workflow updates the Bitsocialnet project board, moving the newly created issue directly to the Done column.

How does conventional commit traceability work with GitHub issues?▼

Conventional commit traceability with GitHub issues works by generating a descriptive issue for recent changes, committing only relevant diffs using conventional commit messages, and closing the issue with the full commit hash to ensure a deterministic link between the work and the issue.

Do I need to manually calculate diffs before creating an issue for completed work?▼

No, you do not need to manually calculate diffs. The workflow automatically calculates relevant diffs from recent changes, commits them with conventional messages to ensure deterministic behavior, and generates a descriptive GitHub issue for the completed work.

What is the best way to ensure traceability for completed work on a GitHub project board?▼

The best way to ensure traceability for completed work is to automate the workflow: generate a descriptive GitHub issue, calculate and commit only relevant diffs with conventional messages, close the issue using the full commit hash, and update the project board to Done.