@ienso/skills-community 1.0.0

package/git-commit-jira/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: git-commit-jira
+description: >
+  Stage and commit changes using the iENSO Git commit message convention. Use
+  this skill whenever the iENSO team asks to commit changes, create a commit,
+  write a commit message, or says "commit this". The skill reads the live Git
+  guidelines from the reference repo, asks for the Jira issue ID and a message
+  summary, then stages and commits following the exact format defined in the
+  guidelines. Trigger for any of: "commit", "commit changes", "create a commit",
+  "commit this", "write a commit message".
+---
+
+# Git Commit
+
+Create a Git commit that follows the iENSO Git commit message convention, as
+defined in the live guidelines in the reference repo.
+
+The **authoritative source for the commit message format** is:
+
+```
+https://github.com/iENSO/ienso-cloud-demo-microservices
+└── 02-development-guidelines/git-guidelines.md
+```
+
+---
+
+## Step 1 — Fetch the Live Commit Message Format
+
+Clone the reference repo into a temporary directory and read the guidelines file.
+
+```bash
+CLONE_DIR=$(mktemp -d)
+git clone git@github.com:iENSO/ienso-cloud-demo-microservices.git "$CLONE_DIR"
+```
+
+Read `$CLONE_DIR/02-development-guidelines/git-guidelines.md` in full and
+extract the commit message format and rules from it. This is the single source
+of truth — do not rely on any format that may have been valid in a prior
+conversation.
+
+Clean up immediately after reading:
+
+```bash
+rm -rf "$CLONE_DIR"
+```
+
+---
+
+## Step 2 — Inspect the Working Tree
+
+Run the following to understand what is staged and unstaged:
+
+```bash
+git status
+git diff --staged
+git diff
+```
+
+Summarise the changes internally so you can suggest a meaningful commit message
+in the next step.
+
+---
+
+## Step 3 — Collect Inputs
+
+Ask questions **one at a time** — send each `AskUserQuestion` call separately
+and wait for the answer before asking the next. Never batch multiple questions
+into a single call.
+
+**Question 1 — Jira issue ID:**
+If the current branch name starts with a Jira key (matching the pattern
+`[A-Z]+-[0-9]+`), extract it and offer it as the default option, asking the
+user to confirm rather than re-enter it. Otherwise ask for the ID (e.g.,
+`CLOUD-1234`) with an "Other" field for typing.
+
+**Question 2 — Commit message summary:**
+Suggest a concise summary derived from the staged diff. Present it as the
+default option so the user can accept it with one click, or type their own via
+"Other".
+
+---
+
+## Step 4 — Stage Files
+
+If there are unstaged changes, ask the user whether to stage all modified and
+deleted tracked files (`git add -u`) or let them specify individual paths. Do
+not stage untracked files automatically — ask first.
+
+---
+
+## Step 5 — Form and Apply the Commit Message
+
+Using the format read from the guidelines in Step 1, construct the full commit
+message and run:
+
+```bash
+git commit -m "$(cat <<'EOF'
+{formatted commit message exactly as the guidelines specify}
+EOF
+)"
+```
+
+Substitute the Jira issue ID and summary collected in Step 3 into the format.
+Do not add any extra lines, signatures, or co-author trailers beyond what the
+guidelines prescribe.
+
+---
+
+## Step 6 — Confirm
+
+After the commit succeeds, print the commit hash and the first line of the
+commit message so the user can verify.
+
+If the commit fails (e.g., pre-commit hook rejection), report the exact error
+output and stop — do not retry automatically.

package/package.json

@@ -0,0 +1,8 @@
+{
+  "name": "@ienso/skills-community",
+  "version": "1.0.0",
+  "description": "iENSO Claude Code skills",
+  "publishConfig": {
+    "access": "public"
+  }
+}