📦 deps(thirdparty): update snapshots

This commit is contained in:
ci[bot]
2026-05-29 08:33:53 +00:00
parent fdb52f1e96
commit 06e0d13d57
1615 changed files with 232858 additions and 0 deletions
@@ -0,0 +1,27 @@
---
description: Adopt Outfitter Stack patterns in a codebase through a phased workflow
argument-hint: [project path]
allowed-tools: Read Write Edit Glob Grep Bash Skill Task
---
# Adopt Outfitter Stack
Target: $ARGUMENTS
## Steps
1. **Load Skills** — Use Skill tool to load `outfitter:context-management` for task persistence.
2. **Plan** — Delegate to **Plan subagent** with `outfitter-stack:stack-audit` to:
- Scan codebase for adoption candidates (throws, console, paths, custom errors)
- Assess scope and effort
- Generate `.outfitter/adopt/` with audit report and phased plan
- Return implementation strategy
3. **Execute** — Delegate phases to `outfitter-stack:stacker`:
- `outfitter-stack:stack-templates` — Scaffold context, logger, dependencies
- `outfitter:tdd` + `outfitter-stack:stack-patterns` — TDD handler conversions
- `outfitter-stack:stack-templates` — Wire CLI/MCP transport layers
- `outfitter-stack:stack-review` — Verify compliance
4. **Persist** — Update Tasks throughout with progress and decisions.
5. **Feedback** — If issues discovered, delegate to `outfitter-stack:stacker` with `outfitter-stack:stack-feedback`.
Proceed without interrupting the user, unless necessary.
@@ -0,0 +1,61 @@
---
description: Quick audit of current file or directory for Outfitter Stack compliance
argument-hint: [file or directory]
allowed-tools: Read Grep Glob Bash(rg *)
---
# Stack Audit
Audit the specified file or directory (or current directory if not provided) for @outfitter/* pattern compliance.
## Target
Path: $ARGUMENTS
## Quick Scans
### Thrown Exceptions
!`rg "throw new" --type ts -c ${ARGUMENTS:-.} 2>/dev/null || echo "0 matches"`
### Console Usage
!`rg "console\.(log|error|warn)" --type ts -c ${ARGUMENTS:-.} 2>/dev/null || echo "0 matches"`
### Hardcoded Paths
!`rg "(homedir|~\/\.)" --type ts -c ${ARGUMENTS:-.} 2>/dev/null || echo "0 matches"`
### Custom Error Classes
!`rg "class \w+Error extends Error" --type ts ${ARGUMENTS:-.} 2>/dev/null || echo "No custom errors found"`
## Task
Based on the scan results above, provide a compliance report:
1. **Summary** - PASS, WARNINGS, or FAIL based on issue count
2. **Critical Issues** - Thrown exceptions, unvalidated paths
3. **High Issues** - Console logging, hardcoded paths, custom errors
4. **Recommendations** - Specific fixes for each issue category
Use the `outfitter-stack:stack-review` skill for detailed compliance checklist reference.
## Report Format
```markdown
## Stack Compliance: [target]
**Status**: PASS | WARNINGS | FAIL
**Issues**: X critical, Y high
### Critical
- [file:line count] Issue description
### High
- [file:line count] Issue description
### Fix Priority
1. First priority fix
2. Second priority fix
```