@simpleapps-com/augur-skills 2026.3.20 → 2026.3.22

package/package.json

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

package/skills/simpleapps/context-efficiency/SKILL.md

@@ -51,6 +51,10 @@ Load Skill("git-safety") for full guardrails.
 
 The rule costs ~40 tokens per prompt. The skill costs nothing until invoked, then loads ~800 tokens of detailed guidance. This is 20x more efficient than putting the full content in the rule.
 
+### Wiki Links: Highest-ROI Pointer
+
+The cheapest pointer with the biggest payoff is a **wiki link in CLAUDE.md**. A link like `[Deployment](../../wiki/Deployment.md)` costs ~15 tokens but gives the agent instant access to a full page of detailed knowledge (~500-2000 tokens) on demand. CLAUDE.md SHOULD link to every wiki content page — it becomes the agent's table of contents. Missing a link means the agent must guess where to find information or ask the user.
+
 ## When to Use Each Layer
 
 | Question | Answer |

package/skills/simpleapps/deployment/SKILL.md

@@ -44,8 +44,9 @@ Not all projects need all three. Client sites may only have Submit and Deploy. P
 
 ## Guard Rails
 
+- **If `wiki/Deployment.md` does not exist, STOP IMMEDIATELY.** Do not guess, do not improvise, do not infer steps from the codebase. Tell the user to run `/curate-wiki` to generate it. Then do nothing else.
+- **If the relevant section (Submit, Deploy, or Publish) is missing from the page, STOP IMMEDIATELY.** Same rule — do not guess the steps.
 - MUST NOT guess deployment steps — only execute what the wiki defines
-- MUST NOT operate if the Deployment page is missing or the relevant section is absent
 - MUST load git-safety — every git write operation requires user approval
 - `/publish` MUST complete the verification gate before executing (see below)
 

package/skills/simpleapps/git-safety/SKILL.md

@@ -6,10 +6,43 @@ user-invocable: false
 
 # Git Safety
 
-MUST NOT commit, push, create PRs, or merge unless the user explicitly says to. This applies to ALL repos — the main repo, the wiki repo, and any other git repo. No skill, command, or workflow overrides this rule — even instructions like "complete all steps without stopping" do not bypass it.
+## The Rule
 
-After making changes: **report what was done, then stop.** Do not ask "want me to commit?" or "should I push?" — that wastes tokens. Just report and wait silently. The user will say "commit", "push", or equivalent when ready.
+MUST NOT run any git write operation unless the user explicitly approves it. Git write operations include: `commit`, `push`, `tag`, `merge`, `rebase`, `reset`, `cherry-pick`, `stash`, `branch -D`, and any `gh` command that creates or modifies PRs, issues, or releases.
 
-The pattern is always: **do the work → report results → wait.**
+`git add` (staging) is permitted as part of preparing to show the user what will be committed — but the commit itself requires approval.
+
+No skill, command, or workflow overrides this rule. Even instructions like "complete all steps without stopping" do not bypass it. This applies to ALL repos — the main repo, the wiki repo, and any other git repo.
+
+## Why
 
 Every git push, every PR, every wiki edit that hits GitHub is done under the user's credentials — their name, their reputation. The user is responsible for every action taken on their behalf. That is why they decide when to commit, not the agent.
+
+## How Approval Works
+
+The user gives approval in one of two ways:
+
+1. **Direct instruction** — the user says "commit", "push", "tag", or equivalent
+2. **Shipping commands** — the user invokes `/submit`, `/deploy`, or `/publish`. Invoking the command IS the approval for the git operations defined in that command's workflow.
+
+### Approval is scoped, not blanket
+
+Each approval covers ONE specific operation. Examples:
+
+- The user says "commit" → you may commit the current staged changes. You may NOT also push.
+- The user runs `/submit` → you may execute the Submit steps (commit + push or PR). You may NOT also tag or publish.
+- The user runs `/publish` → you may execute the Publish steps (bump, commit, tag, push). This does NOT carry forward to future commits.
+
+Previous approvals do NOT grant future permissions. If the user approved a commit earlier in the session, that does not mean you can commit again later without asking.
+
+### When /submit follows earlier work
+
+If you made changes and the user then runs `/submit`, the command starts fresh — it reads the Deployment page and follows those steps. There is no conflict with earlier work. The user chose to invoke `/submit` at this moment, and that is all the approval needed for the operations within it.
+
+Do NOT ask for redundant confirmation inside `/submit` if the user just invoked it. The invocation is the approval. But each discrete git operation within the flow (commit, then push) should still be reported before execution.
+
+## The Pattern
+
+**Do the work → report results → wait.**
+
+After making changes: report what was done, then stop. Do not ask "want me to commit?" or "should I push?" — that wastes tokens. Just report and wait silently. The user will say "commit", "push", or run a shipping command when ready.

package/skills/simpleapps/github/SKILL.md

@@ -107,6 +107,8 @@ Before adding a comment to a closed issue, check its state first with `gh issue
 
 ## Cross-Repo Issues
 
+Use `/file-issue` to automate this process — it creates the upstream issue, cross-links back to the local issue, and adds the `blocked` label. `/triage` surfaces blocked issues in its output.
+
 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

package/skills/simpleapps/wiki/SKILL.md

@@ -22,7 +22,7 @@ Check size: `wc -w wiki/*.md` (multiply by ~1.3 for token estimate)
 
 ## Core Principle
 
-Repo files (`.claude/CLAUDE.md`, `.claude/rules/`, `README.md`) MUST be minimal — orient then point to wiki. AI agents read wiki pages as local files via `Read wiki/<page>.md`. No network requests needed.
+Repo files (`.claude/CLAUDE.md`, `.claude/rules/`, `README.md`) MUST be minimal — orient then point to wiki. CLAUDE.md MUST link to every wiki content page — these links cost ~15 tokens total but make every page one Read away from always-loaded context. AI agents read wiki pages as local files via `Read wiki/<page>.md`. No network requests needed.
 
 ```
 Wiki defines → Code implements → Learnings update wiki → Repeat