@apogeelabs/the-agency 0.4.0 → 0.6.0

package/README.md

@@ -50,6 +50,7 @@ Slash commands invoked in Claude Code sessions.
 | `/prep-pr`        | Pre-submission PR prep and draft creation          |
 | `/review-pr`      | Structured PR review briefing                      |
 | `/weekly-summary` | Weekly synthesis of merged PRs                     |
+| `/dnd-alignment`  | D&D alignment chart from commit history            |
 
 ### AI Context (`.ai/`)
 
@@ -122,14 +123,4 @@ The sync does **not** copy `settings.local.json` or `settings.json` — those ar
 
 ## Development
 
-```bash
-pnpm install
-pnpm build       # Compile TypeScript → dist/
-pnpm test        # Run test suite
-```
-
-Versioning is managed with [changesets](https://github.com/changesets/changesets). To propose a version bump:
-
-```bash
-pnpm changeset
-```
+See the [DEVELOP readme](./DEVELOP.md) for information on how to develop within this repo.

package/dist/manifest.js

@@ -13,7 +13,8 @@ const manifest = {
     { file: "pm.md", description: "Interactive product requirements discovery" },
     { file: "prep-pr.md", description: "Pre-submission PR prep and draft creation" },
     { file: "review-pr.md", description: "Structured PR review briefing" },
-    { file: "weekly-summary.md", description: "Weekly synthesis of merged PRs" }
+    { file: "weekly-summary.md", description: "Weekly synthesis of merged PRs" },
+    { file: "dnd-alignment.md", description: "D&D alignment chart from commit history" }
   ],
   ai: [
     { file: "UnitTestGeneration.md", description: "TypeScript/Jest unit testing style guide" },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@apogeelabs/the-agency",
-  "version": "0.4.0",
+  "version": "0.6.0",
   "description": "Centralized Claude Code agents, commands, and workflows",
   "type": "module",
   "bin": {

package/src/templates/.ai/UnitTestGeneration.md

@@ -414,8 +414,9 @@ Am I in the **outer** `beforeEach`?
     - Always assert **count first**, then **arguments**: `toHaveBeenCalledTimes` before `toHaveBeenCalledWith`
     - Use `toHaveBeenNthCalledWith` for multiple calls with different args
 - **Equality matchers**:
-    - Use `toBe` for primitives (strings, numbers, booleans, null, undefined) — it checks reference equality
+    - Use `toBe` for primitives (strings, integers, booleans, null, undefined) — it checks reference equality
     - Use `toEqual` for objects and arrays — it checks deep equality
+    - Use `toBeCloseTo` for floating-point numbers - it is tolerant of JavaScript's surprising rounding behavior
     - Never use `toBe` on objects (it will fail even if the contents match) or `toEqual` on primitives (it works but is imprecise)
 - **Assertion granularity** (in order of preference):
     1. **Full match** with `toEqual` — assert the entire object/array when possible

package/src/templates/.claude/commands/dnd-alignment.md

@@ -0,0 +1,84 @@
+# D&D Alignment Chart Command
+
+## Goal
+
+Analyze recent commit history and assign a D&D alignment (Lawful Good, Neutral Good, Chaotic Good, Lawful Neutral, True Neutral, Chaotic Neutral, Lawful Evil, Neutral Evil, Chaotic Evil) to each committer based on their commit patterns, message style, and the nature of their work. This is for fun — treat it like a roast, not a performance review.
+
+## Constraints
+
+- **Be funny.** Dry humor, sarcasm, and well-placed jabs are mandatory. This is a comedy bit backed by data, not a Jira report.
+- **Ground it in evidence.** Quote actual commit messages. The humor lands because it's _true_.
+- **Every committer gets a fantasy class/title** in addition to their alignment. The title should reflect their commit personality (e.g., "The Paladin of Tech Debt," "The Test Suite Warlock").
+- **Include commit counts** as supporting data for each person.
+- **Don't pull punches.** If someone's commit history is chaotic, say so. If someone made one commit and vanished, that's comedy gold.
+- **Don't be cruel.** Roast the commits, not the person. There's a line between "your commit history is a hostage negotiation" and actually being mean.
+- **Typos in commit messages are fair game.** Always.
+
+## Step 1: Fetch Commit History
+
+Fetch the last ~30 days of non-merge commits:
+
+```bash
+git log --since="30 days ago" --pretty=format:"%an|%s" --no-merges
+```
+
+Also get per-author commit counts:
+
+```bash
+git log --since="30 days ago" --pretty=format:"%an" --no-merges | sort | uniq -c | sort -rn
+```
+
+## Step 2: Analyze Patterns
+
+For each committer, look for patterns in their commit messages and work:
+
+- **What kind of work do they do?** Feature building, bug fixing, cleanup, infrastructure, tests, docs?
+- **How do they name commits?** Terse? Verbose? Chaotic capitalization?
+- **What's their commit cadence?** Many small commits or few large ones?
+- **Any recurring themes?** Lots of "fix" commits? Lots of "remove" commits? An endless skip/unskip cycle?
+- **Anything funny in the messages?** Typos, frustration, oddly specific wording?
+
+Use these patterns to determine alignment:
+
+- **Lawful**: Follows process, systematic, methodical, adds tooling/enforcement
+- **Chaotic**: Unpredictable patterns, high blast radius, skip/unskip cycles, inconsistent capitalization
+- **Neutral**: Balanced, pragmatic, no strong lean either way
+- **Good**: Improves things for others, security fixes, cleanup, documentation
+- **Evil**: Breaks things (intentionally or otherwise), adds complexity, creates tech debt
+- **Neutral (moral axis)**: Neither improves nor degrades, just ships what's needed
+
+## Step 3: Write the Report
+
+Write the output to `docs/reports/dnd-alignment-chart-YYYY-MM-DD.md` (using today's date).
+
+If a file already exists at that path, overwrite it.
+
+## Output Format
+
+```markdown
+# {Repo Name} — D&D Alignment Chart ({Month} {Year})
+
+Based on ~{N} commits from the last 30 days. This is strictly for fun and not a performance review (unless your alignment is Chaotic Evil, in which case HR will be in touch).
+
+---
+
+## {Name} — **{Alignment}** ({Fantasy Title})
+
+**{N} commits** | Evidence: {quoted commit message snippets}
+
+{1-2 paragraphs of analysis with humor. Reference specific commits. Make it sting a little.}
+
+---
+
+[Repeat for each committer, ordered by commit count descending]
+
+---
+
+_Roll for initiative on that next PR._
+```
+
+## Notes
+
+- If someone has only 1 commit, lean into the mystery of it. One commit is inherently funny.
+- If the repo has a co-author bot (like Claude), don't assign it an alignment — it's an NPC.
+- End with the "Roll for initiative" line. It's tradition now.