tribunal-kit 2.4.6 → 3.0.0

package/.agent/workflows/status.md

@@ -1,125 +1,79 @@
----
-description: Display agent and project status. Progress tracking and status board.
----
-
-# /status — Session View
-
-$ARGUMENTS
-
----
-
-This command shows the current state of the active Tribunal session — what has run, what passed, what was rejected, and what is waiting at the Human Gate.
-
----
-
-## When to Use This
-
-- After starting a multi-agent task to see which reviewers finished
-- When a reviewer rejected code and you want details on the finding
-- To check whether anything is currently at the Human Gate awaiting your decision
-- To get a snapshot of the session before resuming after a break
-
----
-
-## Sub-commands
-
-```
-/status              → Full session view (default)
-/status issues       → Show only REJECTED and WARNING verdicts
-/status gate         → Show what's currently at the Human Gate
-/status agents       → Show only the agent activity table
-/status history      → Show the last 5 completed tribunal sessions
-```
-
----
-
-## Session Dashboard
-
-```
-━━━ Tribunal Session ━━━━━━━━━━━━━━━━━━━━
-
-Mode:     [Generate | Review | Plan | Audit | Swarm]
-Request:  [original prompt or task name]
-Started:  [timestamp]
-
-━━━ Agent Activity ━━━━━━━━━━━━━━━━━━━━━
-
-  logic-reviewer          ✅ APPROVED
-  security-auditor        ❌ REJECTED — 1 CRITICAL issue
-  dependency-reviewer     ✅ APPROVED
-  type-safety-reviewer    ⚠️  WARNING — 1 MEDIUM issue
-  performance-reviewer    🔄 Running...
-  sql-reviewer            ⏸️  Queued
-
-━━━ Blocked Issues ━━━━━━━━━━━━━━━━━━━━━
-
-❌ security-auditor [CRITICAL] — src/routes/user.ts line 34
-   Type: SQL injection via string interpolation
-   Code: db.query(`WHERE id = ${id}`)
-   Fix:  db.query('WHERE id = $1', [id])
-
-⚠️ type-safety-reviewer [MEDIUM] — src/auth/jwt.ts line 12
-   Type: Implicit any in parameter
-   Code: function decodeToken(payload) { ... }
-   Fix:  function decodeToken(payload: JWTPayload) { ... }
-
-━━━ Human Gate ━━━━━━━━━━━━━━━━━━━━━━━━
-
-  Status: ⏸️  Awaiting your decision before any file is written.
-
-  Blocked on: security-auditor rejection (CRITICAL)
-  Action required: Fix the issue and resubmit, or discard.
-
-  Options:
-    ✅ Approve  — write the approved changes to disk
-    🔄 Revise   — send back to the Maker with feedback
-    ❌ Discard  — drop this generation entirely
-```
-
----
-
-## Status Symbols
-
-| Symbol | Meaning |
-|---|---|
-| `✅ APPROVED` | Agent complete — no blocking issues |
-| `🔄 Running` | Agent currently executing |
-| `⏸️ Queued` | Waiting for a prior stage to complete |
-| `❌ REJECTED` | Blocking finding — code cannot proceed |
-| `⚠️ WARNING` | Non-blocking finding — review before approving |
-| `N/A` | Reviewer ran but this domain not present in code |
-
----
-
-## Retry Counter
-
-The status view also shows how many revision attempts have been made:
-
-```
-Maker revision: 2 of 3 (1 remaining before escalation)
-```
-
-After 3 revisions without resolving a CRITICAL rejection, the session halts and reports to the user.
-
----
-
-## Cross-Workflow Navigation
-
-| If /status shows... | Go to |
-|---|---|
-| CRITICAL security rejection | `/review [file]` for focused audit |
-| Multiple rejections across domains | `/tribunal-full` if it hasn't run yet |
-| Session stalled at Human Gate | Review findings and decide: approve/revise/discard |
-| Everything approved, ready to write | Confirm the Human Gate to write to disk |
-
----
-
-## Usage
-
-```
-/status
-/status issues
-/status gate
-/status agents
-/status history
-```
+---
+description: Display agent and project status. Shows task.md progress, last audit results, CI status, and recently modified files. Read-only — no changes made.
+---
+
+# /status — Project Health Dashboard
+
+$ARGUMENTS
+
+---
+
+## What /status Shows
+
+```
+1. Active task progress (from task.md)
+2. Last audit results summary
+3. Recent git activity (last 5 commits)
+4. File modification timestamps (hot files)
+5. Current server status
+```
+
+---
+
+## Execution
+
+```bash
+# 1. Task progress
+cat .gemini/antigravity/brain/*/task.md 2>/dev/null || echo "No active task"
+
+# 2. Recent git activity
+git log --oneline -5
+
+# 3. Recently modified source files (last 24 hours)
+find src/ -name "*.ts" -o -name "*.tsx" -newer package.json 2>/dev/null | head -10
+
+# 4. Server status (non-blocking)
+python .agent/scripts/auto_preview.py status 2>/dev/null
+
+# 5. Quick type check
+npx tsc --noEmit 2>&1 | tail -5
+```
+
+---
+
+## Status Report Format
+
+```
+━━━ Project Status ━━━━━━━━━━━━━━━━━━━━━━━
+
+Project:    [name from package.json]
+Branch:     [git branch]
+Last commit: [hash] — [message] — [time ago]
+
+━━━ Active Task ━━━━━━━━━━━━━━━━━━━━━━━━━
+[task.md content if exists, else: No active task]
+
+━━━ Recent Changes (24h) ━━━━━━━━━━━━━━━━
+  [timestamp] src/app/api/auth/login/route.ts
+  [timestamp] src/lib/auth.ts
+  [timestamp] prisma/schema.prisma
+
+━━━ TypeScript ━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ Zero errors | ❌ N errors found
+
+━━━ Dev Server ━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ Running at http://localhost:3000 | ⭕ Not running
+
+━━━ Next Steps ━━━━━━━━━━━━━━━━━━━━━━━━━
+[any currently incomplete task items from task.md]
+```
+
+---
+
+## Usage
+
+```
+/status              → Full project status
+/status task         → Active task progress only
+/status recent       → Recently modified files only
+```

package/.agent/workflows/strengthen-skills.md

@@ -1,99 +1,139 @@
----
-description: Strengthen skills by appending Tribunal guardrails (LLM Traps, Pre-Flight checklist, VBC Protocol) to any SKILL.md missing them.
----
-
-# /strengthen-skills Workflow
-
-Use this command to audit and harden all skills in `.agent/skills/` that are missing
-the standard Tribunal guardrails block.
-
----
-
-## What It Does
-
-Runs `strengthen_skills.py` against all skill files.  
-For each skill it checks:
-
-1. **Tribunal Integration section** — does it have `🏛️ Tribunal Integration`?
-2. **VBC Protocol** — does it have `Verification-Before-Completion`?
-
-Skills missing either are strengthened by appending the full canonical block:
-- `## 🤖 LLM-Specific Traps`
-- `## 🏛️ Tribunal Integration (Anti-Hallucination)`
-  - Forbidden AI Tropes
-  - Pre-Flight Self-Audit checklist
-  - VBC Protocol
-
-Skills that already have both sections are skipped automatically.
-
----
-
-## Steps
-
-### Step 1 — Dry Run (Always First)
-
-```powershell
-python .agent/scripts/strengthen_skills.py . --dry-run
-```
-
-Review the output. All lines prefixed with `⚠️ [DRY RUN]` are skills that would be strengthened.
-
-> **Human Gate:** If the dry-run output looks correct, continue to Step 2.
-> If unexpected skills are listed, investigate before proceeding.
-
----
-
-### Step 2 — Strengthen All Skills
-
-```powershell
-python .agent/scripts/strengthen_skills.py .
-```
-
----
-
-### Step 3 — Verify Summary
-
-The script prints a final summary:
-```
-✅ Strengthened: N
-⏭️  Skipped:     N
-❌ Errors:       0
-```
-
-Errors must be zero before proceeding. If any errors appear, fix them and re-run.
-
----
-
-### Step 4 — Strengthen a Single Skill (Optional)
-
-To strengthen one specific skill only:
-
-```powershell
-python .agent/scripts/strengthen_skills.py . --skill <skill-name>
-```
-
-Example:
-```powershell
-python .agent/scripts/strengthen_skills.py . --skill brainstorming
-```
-
----
-
-### Step 5 — Custom Skills Directory (Optional)
-
-If skills live in a non-standard location:
-
-```powershell
-python .agent/scripts/strengthen_skills.py . --skills-path /path/to/skills
-```
-
----
-
-## Related Commands
-
-| Command | Purpose |
-|---|---|
-| `/audit` | Full project health audit (includes skills review) |
-| `python .agent/scripts/patch_skills_meta.py .` | Inject version/freshness metadata into frontmatter |
-| `python .agent/scripts/patch_skills_output.py .` | Add Output Format sections to skills missing them |
-| `python .agent/scripts/config_validator.py .` | Validate all agent config consistency |
+---
+description: Strengthen skills by appending Tribunal guardrails (LLM Traps, Pre-Flight checklist, VBC Protocol) to any SKILL.md missing them. Reads each skill, checks for guardrails, appends if missing, skips if present.
+---
+
+# /strengthen-skills — Skill Hardening Pipeline
+
+$ARGUMENTS
+
+---
+
+## When to Use /strengthen-skills
+
+| Use `/strengthen-skills` when... | |
+|:---|:---|
+| New skills were just created | Append guardrails |
+| Auditing existing skills | Check which are missing guardrails |
+| After adding skills from external sources | Harden before activating |
+
+---
+
+## Phase 1 — Skill Inventory
+
+```bash
+# Find all SKILL.md files
+find .agent/skills/ -name "SKILL.md" | sort
+
+# Count total
+find .agent/skills/ -name "SKILL.md" | wc -l
+```
+
+---
+
+## Phase 2 — Guardrail Check
+
+For each SKILL.md, check if it already has guardrails:
+
+```bash
+# Check which skills are MISSING LLM Trap table
+grep -rL "LLM Trap\|LLM Traps\|\*\*Trap\|TRAP TABLE" .agent/skills/*/SKILL.md
+
+# Check which skills are MISSING Pre-Flight checklist
+grep -rL "Pre-Flight\|Pre-flight\|Preflight\|Self-Audit" .agent/skills/*/SKILL.md
+
+# Check which skills are MISSING VBC Protocol
+grep -rL "VBC\|Verify.*Build.*Confirm\|verify.*build.*confirm" .agent/skills/*/SKILL.md
+```
+
+---
+
+## Phase 3 — Append Guardrails (For Missing Skills Only)
+
+For each skill missing guardrails, append the three sections:
+
+```markdown
+---
+
+## 🚨 LLM Trap Table
+
+| Pattern | What AI Does Wrong | What Is Actually Correct |
+|:---|:---|:---|
+| [domain-specific trap 1] | [hallucination] | [correct behavior] |
+| [domain-specific trap 2] | [hallucination] | [correct behavior] |
+| [domain-specific trap 3] | [hallucination] | [correct behavior] |
+
+---
+
+## ✅ Pre-Flight Self-Audit
+
+Before producing any output, verify:
+```
+✅ Did I read the actual files before making claims about them?
+✅ Did I verify all method names against official documentation?
+✅ Did I add // VERIFY: on any uncertain API calls?
+✅ Are all imports from packages that actually exist in package.json?
+✅ Did I test my logic with edge cases (null, empty, 0, max)?
+✅ Did I avoid generating code for more than one module at a time?
+✅ Am I working from evidence, not assumption?
+```
+
+---
+
+## 🔁 VBC Protocol (Verify → Build → Confirm)
+
+```
+VERIFY:  Read the actual codebase before writing anything
+BUILD:   Generate the smallest meaningful unit of code
+CONFIRM: Verify the output is correct before presenting
+```
+```
+
+---
+
+## Phase 4 — Report
+
+After processing all skills:
+
+```
+━━━ Skill Strengthening Report ━━━━━━━━━━━━
+
+Total skills found:     [N]
+Already have guardrails: [N] (skipped)
+Guardrails added:       [N]
+Failed:                  [N]
+
+━━━ Strengthened Skills ━━━━━━━━━━━━━━━━━━
+✅ [skill-name] — LLM Trap + Pre-Flight + VBC added
+✅ [skill-name] — LLM Trap + Pre-Flight + VBC added
+
+━━━ Already Hardened (Skipped) ━━━━━━━━━━━
+⏭️ [skill-name]
+⏭️ [skill-name]
+```
+
+---
+
+## Guardrail Quality Guidelines
+
+LLM Trap tables should be domain-specific — not generic:
+
+```
+❌ Generic (useless):
+"Don't use wrong method names"
+
+✅ Specific (valuable):
+"React 19: useFormState() was renamed to useActionState(). 
+  AI generates old name — import fails at runtime."
+```
+
+The Pre-Flight checklist should match the skill's specific domain — add domain-specific checks beyond the universal ones.
+
+---
+
+## Usage Examples
+
+```
+/strengthen-skills              → Check and harden all skills
+/strengthen-skills nextjs-react-expert → Harden only this skill
+/strengthen-skills --check-only → Audit without modifying
+```