@greeana/jira-dev-workflow 0.1.0 → 0.1.1

package/README.md

@@ -64,6 +64,7 @@ JIRA_API_TOKEN=your_jira_api_token
 ```bash
 npm install
 npm test
+npm run test-install
 node ./bin/jira-dev-workflow.mjs help
 ```
 
@@ -88,7 +89,27 @@ npx -y @greeana/jira-dev-workflow@preview install --preview
 Generate a repo-local skill pinned to an exact published version:
 
 ```bash
-npx -y @greeana/jira-dev-workflow@0.1.0-preview.0 install --version 0.1.0-preview.0
+npx -y @greeana/jira-dev-workflow@0.1.1-preview.0 install --version 0.1.1-preview.0
+```
+
+Smoke-test the current checkout as if it were published by packing it locally and
+running the packaged `install` command against the current repo:
+
+```bash
+npm run test-install
+```
+
+Pass extra `install` flags through the smoke test:
+
+```bash
+npm run test-install -- --force --project-key JDW
+```
+
+To run the same dev-only smoke test against a different repo, change into that repo and
+invoke this checkout's script directly:
+
+```bash
+node --import tsx /absolute/path/to/jira-dev-workflow/scripts/test-install.ts
 ```
 
 This creates:
@@ -102,6 +123,8 @@ This creates:
 It also ensures `.gitignore` contains:
 
 ```text
+.codex/skills/jira-dev-workflow/
+.jira-dev-workflow/config.json
 .jira-dev-workflow/.env.local
 .jira-dev-workflow/state/
 ```
@@ -135,7 +158,7 @@ npx -y @greeana/jira-dev-workflow@preview install --preview
 Install into the current repo and pin the generated skill to an exact published version:
 
 ```bash
-npx -y @greeana/jira-dev-workflow@0.1.0-preview.0 install --version 0.1.0-preview.0
+npx -y @greeana/jira-dev-workflow@0.1.1-preview.0 install --version 0.1.1-preview.0
 ```
 
 Install into the current repo and make the generated skill call a local checkout directly:
@@ -282,10 +305,11 @@ The skill assumes the published package name is `@greeana/jira-dev-workflow`. If
 
 1. Update `version` in `package.json`.
 2. Run `npm test`.
-3. Run `npm pack --dry-run` and confirm only the intended files are included.
-4. Confirm `skill/jira-dev-workflow/SKILL.md` still points to `npx -y @greeana/jira-dev-workflow`.
-5. Publish with `npm publish --access public`.
-6. Smoke-test the published package:
+3. Run `npm run test-install` from this repo, or invoke `scripts/test-install.ts` from a scratch repo.
+4. Run `npm pack --dry-run` and confirm only the intended files are included.
+5. Confirm `skill/jira-dev-workflow/SKILL.md` still points to `npx -y @greeana/jira-dev-workflow`.
+6. Publish with `npm publish --access public`.
+7. Smoke-test the published package:
 
 ```bash
 npx -y @greeana/jira-dev-workflow help

package/bin/jira-dev-workflow.mjs

@@ -1,10 +1,14 @@
 #!/usr/bin/env node
 
 import { spawnSync } from "node:child_process";
+import { createRequire } from "node:module";
 import path from "node:path";
-import { fileURLToPath } from "node:url";
+import { fileURLToPath, pathToFileURL } from "node:url";
 
 const packageDir = path.dirname(path.dirname(fileURLToPath(import.meta.url)));
+const invocationCwd = process.env.INIT_CWD ? path.resolve(process.env.INIT_CWD) : process.cwd();
+const require = createRequire(import.meta.url);
+const tsxLoader = pathToFileURL(require.resolve("tsx")).href;
 const commandMap = new Map([
   ["unit", "tests"],
   ["install", "src/install.ts"],
@@ -58,7 +62,7 @@ function main() {
 
 function runCommand(commandName, commandArgs) {
   if (commandName === "unit") {
-    const result = spawnSync(process.execPath, ["--import", "tsx", "--test", "tests/**/*.test.ts", ...commandArgs], {
+    const result = spawnSync(process.execPath, ["--import", tsxLoader, "--test", "tests/**/*.test.ts", ...commandArgs], {
       cwd: packageDir,
       stdio: "inherit",
     });
@@ -73,8 +77,8 @@ function runCommand(commandName, commandArgs) {
     return;
   }
 
-  const result = spawnSync(process.execPath, ["--import", "tsx", entry, ...commandArgs], {
-    cwd: packageDir,
+  const result = spawnSync(process.execPath, ["--import", tsxLoader, path.join(packageDir, entry), ...commandArgs], {
+    cwd: invocationCwd,
     stdio: "inherit",
   });
 

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@greeana/jira-dev-workflow",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "CLI for Jira-backed development workflows: issue search/create, commit preparation, implementation comments, and imports.",
   "type": "module",
   "bin": {
-    "jira-dev-workflow": "./bin/jira-dev-workflow.mjs"
+    "jira-dev-workflow": "bin/jira-dev-workflow.mjs"
   },
   "files": [
     "bin",
@@ -16,6 +16,7 @@
   ],
   "scripts": {
     "test": "node --import tsx --test tests/**/*.test.ts",
+    "test-install": "node --import tsx ./scripts/test-install.ts",
     "install-workflow": "node --import tsx src/install.ts",
     "test-connection": "node --import tsx src/test-connection.ts",
     "find": "node --import tsx src/find-issue.ts",

package/skill/jira-dev-workflow/SKILL.md

@@ -58,13 +58,14 @@ npx -y @greeana/jira-dev-workflow use --issue JDW-123
 
 5. If there are no open matches and only closed matches exist, create a new issue and pass the best closed match as `--related-issue`.
 6. If UI or preview evidence is useful, attach screenshots or add an implementation report comment.
-7. Preview the commit message with:
+7. Before previewing the commit message, inspect the actual staged diff and derive a concise human message that matches the implementation, not just the Jira issue summary or the draft returned by `prepare-commit`.
+8. Preview the commit message with:
 
 ```bash
 npx -y @greeana/jira-dev-workflow commit --issue JDW-123 -m "Short commit message" --dry-run
 ```
 
-8. After the user confirms, commit with:
+9. After the user confirms, commit with:
 
 ```bash
 npx -y @greeana/jira-dev-workflow commit -m "Short commit message"
@@ -79,15 +80,17 @@ When the user asks to prepare a Jira commit, the agent must treat `prepare-commi
 3. If `openMatches` contains candidates, present them and ask the user which issue to use, or whether to create a new one instead.
 4. If there are no reusable open matches, present the drafted new-issue summary and description and ask the user whether to create that issue.
 5. Do not create a Jira issue, do not save a current issue, do not commit, and do not post comments while still in the `prepare commit` step.
-6. After the user selects an issue or approves creating a new one, preview the final commit message with `commit --dry-run` and ask for confirmation.
-7. Only create the git commit after explicit user confirmation.
-8. Only post an implementation comment or attach files after the user explicitly asks for that, or clearly confirms a workflow that includes posting after commit.
+6. After the user selects an issue or approves creating a new one, inspect `git diff --cached --stat` and, if needed, `git diff --cached` to understand the actual change set before proposing a commit title.
+7. Treat `commitMessageDrafts` as hints only. Do not blindly reuse the Jira issue summary or the draft from `prepare-commit` when the staged diff is narrower or more specific.
+8. Preview the final commit message with `commit --dry-run` and ask for confirmation.
+9. Only create the git commit after explicit user confirmation.
+10. Only post an implementation comment or attach files after the user explicitly asks for that, or clearly confirms a workflow that includes posting after commit.
 
 The intended conversation shape is:
 - User stages changes and asks to prepare a Jira commit.
 - Agent runs `prepare-commit`, shows candidate issues or a new-issue draft, and asks the user to choose.
 - User selects an existing issue or approves creating a new one.
-- Agent shows the final commit message preview and asks for confirmation.
+- Agent inspects the staged diff, proposes a commit message that matches the actual implementation, then shows the final commit message preview and asks for confirmation.
 - User confirms.
 - Agent commits, and only then posts back to Jira if the user asked for posting.
 
@@ -97,6 +100,8 @@ The intended conversation shape is:
 - If only closed issues match, create a new issue and relate it to the best closed match.
 - Prefer `npx -y @greeana/jira-dev-workflow prepare-commit --json` for commit workflows because it includes both Jira matches and draft commit text.
 - Use `npx -y @greeana/jira-dev-workflow current` if you need to confirm the selected issue before commit.
+- Read the staged diff before proposing the final commit title.
+- Treat `commitMessageDrafts` as a starting point, not the final message.
 - For commit messages, keep the human part short because the Jira key is prefixed automatically by the workflow.
 - For implementation reports with screenshots, prefer `comment --text-file ... --inline-file ...` and place screenshot markers as standalone paragraphs inside the text:
   - `[[inline-file]]` inserts the next screenshot in order

package/src/install.ts

@@ -11,7 +11,12 @@ const localWorkflowDir = ".jira-dev-workflow";
 const localConfigFile = path.join(localWorkflowDir, "config.json");
 const localEnvFile = path.join(localWorkflowDir, ".env.local");
 const localStateDir = path.join(localWorkflowDir, "state");
-const gitignoreEntries = [".jira-dev-workflow/.env.local", ".jira-dev-workflow/state/"];
+const gitignoreEntries = [
+  ".codex/skills/jira-dev-workflow/",
+  ".jira-dev-workflow/config.json",
+  ".jira-dev-workflow/.env.local",
+  ".jira-dev-workflow/state/",
+];
 
 export type InstallOptions = {
   force: boolean;