@simpleapps-com/augur-skills 2026.3.2 → 2026.3.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@simpleapps-com/augur-skills",
-  "version": "2026.03.2",
+  "version": "2026.03.4",
   "description": "Install curated Claude Code skills",
   "license": "MIT",
   "type": "module",

package/skills/simpleapps/github/SKILL.md

@@ -100,6 +100,29 @@ gh issue close <number> --repo simpleapps-com/<repo> --comment "message"
 
 Include `Closes #N` in commit body to auto-close issues.
 
+### Commenting on existing issues
+
+Before adding a comment to a closed issue, check its state first with `gh issue view`. If the issue is closed but the problem still exists, reopen it with `gh issue reopen` before commenting — a comment on a closed issue is easily missed.
+
+## Cross-Repo Issues
+
+When a project hits a blocker that depends on another team's repo, create two issues and keep working:
+
+1. **Local issue** (in the site/project repo) — describe the impact and what's blocked
+2. **Upstream issue** (in the dependency repo) — describe the ask, include reproduction steps or specifics
+3. **Cross-link** — reference the other issue using `simpleapps-com/repo#N` syntax in both issue bodies
+4. **Don't block** — continue with other tasks while waiting for the upstream fix
+
+Target repos:
+
+| Dependency | Repo |
+|------------|------|
+| Backend microservices | `simpleapps-com/augur` |
+| Shared frontend packages | `simpleapps-com/augur-packages` |
+| TypeScript API SDK | `simpleapps-com/augur-api` |
+
+Example cross-link in issue body: `Upstream: simpleapps-com/augur#44` or `Local impact: simpleapps-com/spotweldingsupplies#3`
+
 ## Pull Requests
 
 ```bash

package/skills/simpleapps/project-defaults/SKILL.md

@@ -65,6 +65,7 @@ The repo contains `.claude/rules/` and `.claude/commands/` with project-specific
 
 ```bash
 mkdir -p {project}/.claude
+mkdir -p {project}/repo/.claude/rules {project}/repo/.claude/commands
 ln -sf ../repo/.claude/rules {project}/.claude/rules
 ln -sf ../repo/.claude/commands {project}/.claude/commands
 ```
@@ -101,7 +102,7 @@ Every project SHOULD configure `.claude/settings.local.json` with these deny rul
 
 Why each is denied:
 
-- **`cd`** — Use `git -C` or tool-specific flags (`--repo`, `-C`) instead. `cd` loses working directory context.
+- **`cd`** — MUST NOT use in any Bash command, including compound commands (`cd /path && git`). Use `git -C repo` for git, path arguments for everything else. Compound cd+git commands trigger an unblockable Claude Code security prompt that interrupts the user even when `cd` is denied.
 - **`cat`** — Use the Read tool instead.
 - **`sed`** — Use the Edit tool instead.
 - **`grep`** — Use the Grep tool instead.
@@ -136,6 +137,7 @@ mkdir {project} && cd {project}
 git clone https://github.com/simpleapps-com/<name>.git repo
 git clone https://github.com/simpleapps-com/<name>.wiki.git wiki
 mkdir -p wip tmp .simpleapps .claude
+mkdir -p repo/.claude/rules repo/.claude/commands
 ln -sf ../repo/.claude/rules .claude/rules
 ln -sf ../repo/.claude/commands .claude/commands
 ```

package/skills/simpleapps/work-habits/SKILL.md

@@ -19,6 +19,8 @@ Prefer dedicated tools over Bash equivalents — they are faster, need no permis
 
 Reserve Bash for commands that have no dedicated tool equivalent.
 
+MUST NOT use `cd` in any Bash command — not even in compound commands like `cd /path && git log`. Use `git -C repo` for git, and path arguments for everything else. The `cd` deny rule does not suppress Claude Code's built-in security prompt for compound cd+git commands, so any `cd` usage will interrupt the user.
+
 ## Protect the context window
 
 - Prefer targeted searches over broad exploration