ai-engineering-kit 0.2.0 → 0.3.0

package/dist/cli.js

@@ -22,29 +22,77 @@ function parseManifest(json) {
 
 // src/catalog/definition.ts
 var CATEGORIES = [
-  { id: "core-workflow", label: "Core workflow", from: "skills/core-workflow", to: "ai/skills" },
-  { id: "engineering", label: "Engineering", from: "skills/engineering", to: "ai/skills" },
-  { id: "productivity", label: "Productivity", from: "skills/productivity", to: "ai/skills" },
-  { id: "misc", label: "Misc", from: "skills/misc", to: "ai/skills" }
+  {
+    id: "core-workflow",
+    label: "Core workflow",
+    hint: "End-to-end loop: kickoff \u2192 PRD \u2192 plan \u2192 implement \u2192 review \u2192 verify",
+    from: "skills/core-workflow",
+    to: "ai/skills"
+  },
+  {
+    id: "engineering",
+    label: "Engineering",
+    hint: "Daily coding skills \u2014 TDD, debugging, triage, architecture (from mattpocock/skills)",
+    from: "skills/engineering",
+    to: "ai/skills"
+  },
+  {
+    id: "productivity",
+    label: "Productivity",
+    hint: "Workflow helpers \u2014 grilling, handoff, teaching, concise mode (from mattpocock/skills)",
+    from: "skills/productivity",
+    to: "ai/skills"
+  },
+  {
+    id: "misc",
+    label: "Misc",
+    hint: "Occasional utilities \u2014 git guardrails, pre-commit, scaffolding (from mattpocock/skills)",
+    from: "skills/misc",
+    to: "ai/skills"
+  }
 ];
 var TREE_COMPONENTS = [
-  { id: "docs-foundations", label: "docs/foundations scaffold", from: "docs/foundations", to: "docs/foundations" },
-  { id: "ai-workspace", label: "ai/ workspace dirs", from: "ai-workspace", to: "ai" }
+  {
+    id: "docs-foundations",
+    label: "Foundation docs",
+    hint: "Starter docs for product vision, guidelines, and technical decisions (docs/foundations/)",
+    from: "docs/foundations",
+    to: "docs/foundations"
+  },
+  {
+    id: "ai-workspace",
+    label: "Workspace folders",
+    hint: "Folders the skills write to: brainstorms, PRDs, plans, reviews (ai/)",
+    from: "ai-workspace",
+    to: "ai"
+  }
 ];
 var COMPONENTS = [
-  { id: "skills", label: "Skills", unlocks: "categories" },
-  ...TREE_COMPONENTS.map((t) => ({ id: t.id, label: t.label })),
-  { id: "entry-files", label: "Agent entry files", unlocks: "agents" }
+  {
+    id: "skills",
+    label: "Skills",
+    hint: "Reusable AI playbooks the agent runs on demand (plan, implement, review, debug\u2026)",
+    unlocks: "categories"
+  },
+  ...TREE_COMPONENTS.map((t) => ({ id: t.id, label: t.label, hint: t.hint })),
+  {
+    id: "entry-files",
+    label: "Agent entry files",
+    hint: "Instruction files that wire your coding agent to the skills (CLAUDE.md / AGENTS.md)",
+    unlocks: "agents"
+  }
 ];
 var AGENTS = [
   {
     id: "claude-code",
     label: "Claude Code",
+    hint: "Adds CLAUDE.md + a .claude/skills/ symlink for native skill discovery",
     files: [{ from: "agents/claude-code.CLAUDE.md", to: "CLAUDE.md", substitute: true }]
   },
   {
     id: "codex",
     label: "Codex",
+    hint: "Adds AGENTS.md referencing ai/skills/",
     files: [{ from: "agents/codex.AGENTS.md", to: "AGENTS.md", substitute: true }]
   }
 ];
@@ -295,13 +343,13 @@ import { multiselect, text, isCancel, cancel } from "@clack/prompts";
 
 // src/menu/menu.ts
 function componentOptions() {
-  return COMPONENTS.map((c) => ({ value: c.id, label: c.label }));
+  return COMPONENTS.map((c) => ({ value: c.id, label: c.label, hint: c.hint }));
 }
 function categoryOptions() {
-  return CATEGORIES.map((c) => ({ value: c.id, label: c.label }));
+  return CATEGORIES.map((c) => ({ value: c.id, label: c.label, hint: c.hint }));
 }
 function agentOptions() {
-  return AGENTS.map((a) => ({ value: a.id, label: a.label }));
+  return AGENTS.map((a) => ({ value: a.id, label: a.label, hint: a.hint }));
 }
 function buildSelection(answers) {
   return {
@@ -319,33 +367,26 @@ function required(value) {
   }
   return value;
 }
-async function promptForSelection(projectDir) {
-  const components = required(
+var allValues = (options) => options.map((o) => o.value);
+async function pickAll(message, options) {
+  return required(
     await multiselect({
-      message: "Which parts do you want to install?",
-      options: componentOptions(),
+      message: `${message} (everything is pre-selected \u2014 toggle off what you don't want)`,
+      options,
+      initialValues: allValues(options),
       required: true
     })
   );
+}
+async function promptForSelection(projectDir) {
+  const components = await pickAll("Which parts do you want to install?", componentOptions());
   let categories = [];
   if (components.includes("skills")) {
-    categories = required(
-      await multiselect({
-        message: "Which skill categories?",
-        options: categoryOptions(),
-        required: true
-      })
-    );
+    categories = await pickAll("Which skill categories?", categoryOptions());
   }
   let agents = [];
   if (components.includes("entry-files")) {
-    agents = required(
-      await multiselect({
-        message: "Which coding agents?",
-        options: agentOptions(),
-        required: true
-      })
-    );
+    agents = await pickAll("Which coding agents?", agentOptions());
   }
   const projectName = required(
     await text({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-engineering-kit",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "An opinionated, agent-agnostic AI-development kit — disciplined skills plus a structured workspace — installed and updated through one npx command.",
   "type": "module",
   "license": "MIT",

package/template/skills/core-workflow/commit-organizer/SKILL.md

@@ -0,0 +1,174 @@
+---
+name: commit-organizer
+description: Analyze all code changes across one or more repos and organize them into logical, separate conventional commits. Use when you have many unstaged/staged changes and want clean, atomic commits instead of one big commit.
+argument-hint: "[repo-path]"
+allowed-tools: Read, Bash(git *), Glob, Grep
+---
+
+# Commit Organizer
+
+Analyze all code changes (staged and unstaged) in the current directory. If the directory contains multiple git repos (a workspace root), analyze each repo independently. Organize changes into logical, atomic conventional commits.
+
+## How It Works
+
+1. Detect whether the current directory is a git repo or a workspace containing multiple repos
+2. For each repo, collect all modified, added, and untracked files
+3. Read the diffs and new file contents to understand what each change does
+4. Group related changes into logical commit units (e.g., a permission change + its test = one commit)
+5. Order commits so dependencies come first
+6. Present the commit plan to the user for approval
+7. Execute the commits one by one
+
+## Commit Message Rules
+
+- Use conventional commits: `type(scope): description`
+- Types: `feat`, `fix`, `refactor`, `style`, `docs`, `test`, `chore`
+- One line only, max 72 characters
+- Describe WHAT the change does from the user's perspective, not HOW
+- Use imperative mood: "add", "fix", "ensure", "change", not "added", "fixes"
+- Be specific — name the feature, the bug, the thing that changed
+
+### Good Examples
+
+```
+feat: add per-card CSV export to Insights dashboard cards
+feat: ensure bulk data export is only available to superAdmin users
+fix: use YYYY/MM/DD date format in all CSV exports
+refactor: extract shared RQS value mapping to exportUtils
+feat: add export audit log with search and pagination
+chore: add i18n keys for export and audit log UI
+```
+
+### Bad Examples
+
+```
+update code                          # too vague
+feat: changes to export              # what changes?
+fix: fix bug                         # what bug?
+feat: add new feature                # what feature?
+refactor: refactor stuff             # what stuff?
+feat: implement export refactoring   # describes the task, not the change
+```
+
+## Grouping Strategy
+
+Group changes into commits by **logical intent**, not by file type:
+
+- A backend permission change + frontend visibility change for the same feature = ONE commit
+- A new utility file + the component that uses it = ONE commit (if tightly coupled)
+- i18n keys can be grouped with the feature that uses them, or in a separate commit if they span multiple features
+- Unrelated changes to different features = SEPARATE commits
+- A new GraphQL schema + resolver + frontend query/mutation for one feature = ONE commit
+
+When in doubt, prefer fewer, more meaningful commits over many tiny ones.
+
+## Execution
+
+### Step 1: Detect Repos
+
+If `$ARGUMENTS` is provided, use it as the path. Otherwise use the current working directory.
+
+```bash
+# Check if current dir is a git repo
+git rev-parse --git-dir 2>/dev/null
+
+# If not, find git repos one level deep (workspace mode)
+for dir in */; do
+  if [ -d "$dir/.git" ]; then
+    echo "$dir"
+  fi
+done
+```
+
+### Step 2: Collect Changes Per Repo
+
+For each repo, run:
+
+```bash
+git status -u          # all changes including untracked (never use -uall)
+git diff               # unstaged changes
+git diff --cached      # staged changes
+```
+
+For untracked files, read their contents to understand what they add.
+
+### Step 3: Analyze and Group
+
+Read all diffs and new files. For each change, determine:
+- What feature or concern does this belong to?
+- Is it a feat, fix, refactor, style, docs, test, or chore?
+- What other changes is it related to?
+
+Group into commit units. Each unit has:
+- A list of files to stage
+- A commit message
+- A brief rationale (for the user to review)
+
+### Step 4: Present Plan
+
+Show the user a numbered list of proposed commits in order:
+
+```
+Repository: cliezen-graph
+
+  1. feat: restrict bulk CSV export to superAdmin users
+     Files: routes/exportCsv.js
+     
+  2. fix: use YYYY/MM/DD date format in bulk CSV exports
+     Files: routes/exports/csv.js
+
+Repository: cliezen-dashboard
+
+  3. feat: add shared export utilities and CSV formatters
+     Files: src/utils/exportUtils.js, src/utils/cardExportFormatters.js
+
+  4. feat: add per-card CSV export to Insights dashboard cards
+     Files: src/composables/useCardExport.js, src/components/Insights/DashCard.vue, src/graphql/mutations.js
+```
+
+Ask the user: "Does this commit plan look good? You can adjust, reorder, merge, or split any commits."
+
+Wait for approval before proceeding. If the user says "go" or "yes" or "looks good", execute. If they request changes, adjust and re-present.
+
+### Step 5: Execute Commits
+
+For each commit unit, in order:
+
+```bash
+cd <repo-path>
+git add <file1> <file2> ...    # stage only files for this commit
+git commit -m "<message>"       # commit with the planned message
+```
+
+After each commit, confirm success before moving to the next.
+
+If a commit fails (e.g., pre-commit hook), stop and report the error. Do not skip or force.
+
+### Step 6: Summary
+
+After all commits are done, show a summary:
+
+```
+Done! Created N commits across M repos:
+
+cliezen-graph (2 commits):
+  abc1234 feat: restrict bulk CSV export to superAdmin users
+  def5678 fix: use YYYY/MM/DD date format in bulk CSV exports
+
+cliezen-dashboard (4 commits):
+  111aaaa feat: add shared export utilities and CSV formatters
+  222bbbb feat: add per-card CSV export to Insights dashboard cards
+  ...
+```
+
+## Edge Cases
+
+- If there are no changes in a repo, skip it silently
+- If all changes belong to one logical unit, make one commit (don't force artificial splits)
+- If a file has changes belonging to two different features, note this and ask the user how to handle it (commit the whole file with the more significant change, or suggest the user manually split it with `git add -p`)
+- Never run `git add .` or `git add -A` — always stage specific files
+- Never amend existing commits
+- Never force push
+- Never use `--no-verify`
+- Never add Co-Authored-By, Signed-off-by, or any AI attribution trailers to commit messages
+- Commit messages are the developer's own — no mention of Claude, AI, or any tool