make-closed-issue

name	make-closed-issue
description	Create a GitHub issue from recent changes, commit only relevant diffs, close the issue with the commit hash, and add it to the bitsocialnet project board as Done. Use when the user says "make closed issue", "close issue", or wants to create a tracked, already-resolved GitHub issue for completed work.

Make Closed Issue

Creates a GitHub issue, commits relevant changes, closes the issue with the commit hash, and adds it to the project board — all in one workflow.

Inputs

• What changed and why (from prior conversation context)
• Uncommitted or staged git changes in the working tree

Workflow

1. Determine label(s)

Ask the user using AskQuestion (multi-select):

Option	When
bug	Bug fix
enhancement	New feature
bug + enhancement	New feature that also fixes a bug
documentation	README, AGENTS.md, docs-only changes

2. Review diffs for relevance

git status
git diff
git diff --cached

Identify which files relate to the work done in this conversation. Only relevant changes get committed. Unrelated files must be excluded from staging.

Important: git add -p and git add -i are not available (interactive mode unsupported). If a file has mixed relevant/irrelevant changes, include the entire file and note the caveat to the user.

3. Generate issue title and description

From the conversation context:

• Title: Short, present-tense, describes the problem (not the solution). Use backticks for UI elements, code, or literal strings (e.g. Post page `Update` button disabled and `Auto` alert unclear).
• Description: 2-3 sentences about the problem. Use backticks for UI element names (Update, Auto), function/code references (useReplies().reset()), and literal text strings. Write as if the issue hasn't been fixed yet.

4. Create the issue

gh issue create \
  --repo bitsocialnet/bitsocial-web \
  --title "ISSUE_TITLE" \
  --body "ISSUE_DESCRIPTION" \
  --label "LABEL1,LABEL2" \
  --assignee plebe1us

Capture the issue number from the output.

5. Commit relevant changes

Stage only the relevant files:

git add file1.ts file2.tsx ...

Commit using Conventional Commits with scope:

git commit -m "$(cat <<'EOF'
type(scope): concise title

Optional 1-sentence description only if the title isn't self-explanatory.
EOF
)"

• Types: fix, feat, perf, refactor, docs, chore
• Scope: area of the codebase (e.g., reply-modal, markdown, routing)
• Prefer title-only commits — skip description when the title is exhaustive

6. Comment with commit hash and close

Use the full (40-character) commit hash, not the short form.

COMMIT_HASH=$(git rev-parse HEAD)
gh issue comment ISSUE_NUMBER --repo bitsocialnet/bitsocial-web --body "$COMMIT_HASH"
gh issue close ISSUE_NUMBER --repo bitsocialnet/bitsocial-web

7. Add to project board

Use the GitHub MCP tools (not gh CLI) for project operations.

Add the issue to the project:

projects_write → add_project_item
  owner: bitsocialnet
  project_number: 1
  item_type: issue
  item_owner: bitsocialnet
  item_repo: bitsocial-web
  issue_number: <ISSUE_NUMBER>

Set Status to "Done":

projects_write → update_project_item
  owner: bitsocialnet
  project_number: 1
  item_id: <from add response>
  updated_field: { "id": 251829983, "value": "98236657" }

Assignees and labels are inherited from the issue (set in step 4) — no separate project update needed.

8. Report summary

Print a summary to the user:

Issue #NUMBER created, committed, closed, and added to project board.
  Commit: HASH
  Labels: label1, label2
  Project: bitsocial-web → Done
  URL: https://github.com/bitsocialnet/bitsocial-web/issues/NUMBER