moai-adk 0.4.5__py3-none-any.whl → 0.4.7__py3-none-any.whl

moai_adk/templates/.claude/skills/moai-foundation-tags/SKILL.md

@@ -1,86 +1,113 @@
 ---
-
 name: moai-foundation-tags
-description: Scans @TAG markers directly from code and generates inventory (CODE-FIRST). Use when establishing or auditing TAG conventions.
+version: 2.0.0
+created: 2025-10-22
+updated: 2025-10-22
+status: active
+description: TAG inventory management and orphan detection (CODE-FIRST principle).
+keywords: ['tag', 'inventory', 'traceability', 'code-first']
 allowed-tools:
   - Read
   - Bash
-  - Write
-  - Edit
-  - TodoWrite
 ---
 
-# Alfred TAG Scanning
+# Foundation Tags Skill
 
 ## Skill Metadata
+
 | Field | Value |
 | ----- | ----- |
-| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
-| Auto-load | SessionStart (foundation bootstrap) |
-| Trigger cues | TAG scanning, traceability audits, orphan TAG remediation requests. |
+| **Skill Name** | moai-foundation-tags |
+| **Version** | 2.0.0 (2025-10-22) |
+| **Allowed tools** | Read (read_file), Bash (terminal) |
+| **Auto-load** | On demand when keywords detected |
+| **Tier** | Foundation |
 
-## What it does
+---
 
-Scans all @TAG markers (SPEC/TEST/CODE/DOC) directly from codebase and generates TAG inventory without intermediate caching (CODE-FIRST principle).
+## What It Does
 
-## When to use
+TAG inventory management and orphan detection (CODE-FIRST principle).
 
-- Activates when scanning or auditing TAG chains or locating orphaned tags.
-- "TAG Scan", "TAG List", "TAG Inventory"
-- Automatically invoked by `/alfred:3-sync`
-- “Find orphan TAG”, “Check TAG chain”
+**Key capabilities**:
+- ✅ Best practices enforcement for foundation domain
+- ✅ TRUST 5 principles integration
+- ✅ Latest tool versions (2025-10-22)
+- ✅ TDD workflow support
 
-## How it works
+---
 
-**CODE-FIRST Scanning**:
-```bash
-# Direct code scan without intermediate cache
-rg '@(SPEC|TEST|CODE|DOC):' -n .moai/specs/ tests/ src/ docs/
-```
+## When to Use
 
-**TAG Inventory Generation**:
-- Lists all TAGs with file locations
-- Detects orphaned TAGs (no corresponding SPEC/TEST/CODE)
-- Identifies broken links in TAG chain
-- Reports duplicate IDs
+**Automatic triggers**:
+- Related code discussions and file patterns
+- SPEC implementation (`/alfred:2-run`)
+- Code review requests
 
-**TAG Chain Verification**:
-- @SPEC → @TEST → @CODE → @DOC connection check
-- Ensures traceability across all artifacts
+**Manual invocation**:
+- Review code for TRUST 5 compliance
+- Design new features
+- Troubleshoot issues
 
-## Examples
-```markdown
-- Scan standard documents and report missing sections.
-- Changed regulations are reflected in CLAUDE.md.
-```
+---
 
 ## Inputs
-- Project standard documents (e.g. `CLAUDE.md`, `.moai/config.json`).
-- Latest printouts from relevant sub-agents.
+
+- Language-specific source directories
+- Configuration files
+- Test suites and sample data
 
 ## Outputs
-- Templates or policy summaries conforming to the MoAI-ADK standard.
-- Reusable rules/checklists.
+
+- Test/lint execution plan
+- TRUST 5 review checkpoints
+- Migration guidance
 
 ## Failure Modes
-- When required standard files are missing or have limited access rights.
-- When conflicting policies are detected and coordination is required.
+
+- When required tools are not installed
+- When dependencies are missing
+- When test coverage falls below 85%
 
 ## Dependencies
-- There is great synergy when called together with cc-manager.
 
-## References
-- BurntSushi. "ripgrep User Guide." https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md (accessed 2025-03-29).
-- ReqView. "Requirements Traceability Matrix Guide." https://www.reqview.com/doc/requirements-traceability-matrix/ (accessed 2025-03-29).
+- Access to project files via Read/Bash tools
+- Integration with `moai-foundation-langs` for language detection
+- Integration with `moai-foundation-trust` for quality gates
+
+---
+
+## References (Latest Documentation)
+
+_Documentation links updated 2025-10-22_
+
+---
 
 ## Changelog
-- 2025-03-29: Foundation skill templates have been enhanced to align with best practice structures.
 
-## Works well with
+- **v2.0.0** (2025-10-22): Major update with latest tool versions, comprehensive best practices, TRUST 5 integration
+- **v1.0.0** (2025-03-29): Initial Skill release
+
+---
+
+## Works Well With
 
-- moai-foundation-trust
-- moai-foundation-specs
+- `moai-foundation-trust` (quality gates)
+- `moai-alfred-code-reviewer` (code review)
+- `moai-essentials-debug` (debugging support)
+
+---
 
 ## Best Practices
-- When changing standards, the reason for change and supporting documents are recorded.
-- Follow the single source principle and avoid modifying the same item in multiple places.
+
+✅ **DO**:
+- Follow foundation best practices
+- Use latest stable tool versions
+- Maintain test coverage ≥85%
+- Document all public APIs
+
+❌ **DON'T**:
+- Skip quality gates
+- Use deprecated tools
+- Ignore security warnings
+- Mix testing frameworks

moai_adk/templates/.claude/skills/moai-foundation-tags/examples.md

@@ -0,0 +1,29 @@
+# moai-foundation-tags - Working Examples
+
+_Last updated: 2025-10-22_
+
+## Example 1: Basic Setup
+
+```bash
+# Setup commands
+# ...
+```
+
+## Example 2: TDD Workflow
+
+```bash
+# RED: Write failing test
+# GREEN: Implement feature
+# REFACTOR: Improve code
+```
+
+## Example 3: Quality Gate
+
+```bash
+# Run quality checks
+# Verify coverage ≥85%
+```
+
+---
+
+_For more examples, see SKILL.md reference section_

moai_adk/templates/.claude/skills/moai-foundation-tags/reference.md

@@ -0,0 +1,28 @@
+# moai-foundation-tags - CLI Reference
+
+_Last updated: 2025-10-22_
+
+## Quick Reference
+
+### Installation
+
+```bash
+# Installation commands
+```
+
+### Common Commands
+
+```bash
+# Test
+# Lint
+# Format
+# Build
+```
+
+## Tool Versions (2025-10-22)
+
+_No specific tool versions (workflow/process Skill)_
+
+---
+
+_For detailed usage, see SKILL.md_

moai_adk/templates/.claude/skills/moai-foundation-trust/SKILL.md

@@ -1,5 +1,4 @@
 ---
-
 name: moai-foundation-trust
 description: Validates TRUST 5-principles (Test 85%+, Readable, Unified, Secured, Trackable). Use when aligning with TRUST governance.
 allowed-tools:
@@ -8,6 +7,8 @@ allowed-tools:
   - Edit
   - Bash
   - TodoWrite
+version: 2.0.0
+created: 2025-10-22
 ---
 
 # Foundation: TRUST Validation
@@ -15,72 +16,292 @@ allowed-tools:
 ## Skill Metadata
 | Field | Value |
 | ----- | ----- |
-| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
-| Auto-load | SessionStart (foundation bootstrap) |
-| Trigger cues | TRUST compliance checks, release readiness reviews, quality gate enforcement. |
+| Version | 2.0.0 |
+| Created | 2025-10-22 |
+| Allowed tools | Read, Write, Edit, Bash, TodoWrite |
+| Auto-load | SessionStart (foundation bootstrap), `/alfred:3-sync` |
+| Trigger cues | TRUST compliance checks, release readiness reviews, quality gate enforcement |
 
 ## What it does
 
-Validates MoAI-ADK's TRUST 5-principles compliance to ensure code quality, testability, security, and traceability.
+Validates MoAI-ADK's TRUST 5-principles compliance using the latest 2025 testing frameworks, SAST tools, and CI/CD automation to ensure code quality, testability, security, and traceability.
 
 ## When to use
 
-- Activates when TRUST compliance or release readiness needs to be evaluated.
+- Activates when TRUST compliance or release readiness needs evaluation
 - "Check the TRUST principle", "Quality verification", "Check code quality"
 - Automatically invoked by `/alfred:3-sync`
 - Before merging PR or releasing
+- During CI/CD pipeline execution
 
 ## How it works
 
-**T - Test First**:
-- Checks test coverage ≥85% (pytest, vitest, go test, cargo test, etc.)
-- Verifies TDD cycle compliance (RED → GREEN → REFACTOR)
+### T - Test First (Coverage ≥85%)
+
+**Supported Testing Frameworks (2025-10-22)**:
+
+| Language | Framework | Version | Coverage Tool | Command |
+| --- | --- | --- | --- | --- |
+| Python | pytest | 8.4.2 | pytest-cov | `pytest --cov=src --cov-report=term-missing --cov-fail-under=85` |
+| TypeScript/JS | Vitest | 2.0.5 | @vitest/coverage-v8 | `vitest run --coverage --coverage.thresholds.lines=85` |
+| JavaScript | Jest | 29.x | built-in | `jest --coverage --coverageThreshold='{"global":{"lines":85}}'` |
+| Go | testing | 1.23 | built-in | `go test ./... -cover -coverprofile=coverage.out` |
+| Rust | cargo test | 1.82.0 | tarpaulin | `cargo tarpaulin --out Xml --output-dir coverage/ --fail-under 85` |
+| Java/Kotlin | JUnit | 5.10.x | JaCoCo | `./gradlew test jacocoTestReport` |
+| Dart/Flutter | flutter test | 3.x | built-in | `flutter test --coverage --coverage-path=coverage/lcov.info` |
+
+**TDD Cycle Verification**:
+- RED: Failing test exists before implementation (`@TEST:ID`)
+- GREEN: Implementation passes test (`@CODE:ID`)
+- REFACTOR: Code quality improvements documented
+
+**Quality Gates**:
+- Line coverage ≥85%
+- Branch coverage ≥80%
+- No skipped tests in production code
+- Test execution time <5 minutes for unit tests
+
+### R - Readable (Code Quality)
+
+**Constraints**:
+- File ≤300 LOC
+- Function ≤50 LOC
+- Parameters ≤5
+- Cyclomatic complexity ≤10
+
+**Linting Tools (2025-10-22)**:
+
+| Language | Linter | Version | Command |
+| --- | --- | --- | --- |
+| Python | ruff | 0.6.x | `ruff check . --fix` |
+| TypeScript/JS | Biome | 1.9.x | `biome check --apply .` |
+| JavaScript | ESLint | 9.x | `eslint . --fix` |
+| Go | golangci-lint | 1.60.x | `golangci-lint run` |
+| Rust | clippy | 1.82.0 | `cargo clippy -- -D warnings` |
+| Java | Checkstyle | 10.x | `./gradlew checkstyleMain` |
+
+**Formatting Standards**:
+- Consistent indentation (language-specific)
+- Meaningful variable/function names
+- Early return pattern (guard clauses)
+- Comments only for "why", not "what"
 
-**R - Readable**:
-- File ≤300 LOC, Function ≤50 LOC, Parameters ≤5, Complexity ≤10
+### U - Unified (Architecture)
 
-**U - Unified**:
-- SPEC-driven architecture consistency, Clear module boundaries
+**Verification Points**:
+- SPEC-driven architecture consistency
+- Clear module boundaries and responsibilities
+- Type safety (TypeScript strict mode, mypy strict, etc.)
+- Interface/Protocol compliance
+- Dependency direction (inward toward domain)
 
-**S - Secured**:
-- Input validation, No hardcoded secrets, Access control
+**Type Checking Tools**:
+
+| Language | Tool | Version | Command |
+| --- | --- | --- | --- |
+| Python | mypy | 1.11.x | `mypy src/ --strict` |
+| TypeScript | tsc | 5.6.x | `tsc --noEmit --strict` |
+| Go | built-in | 1.23 | `go vet ./...` |
+| Rust | built-in | 1.82.0 | `cargo check` |
+
+### S - Secured (Security & SAST)
+
+**SAST Tools (2025-10-22)**:
+
+| Tool | Version | Purpose | Command |
+| --- | --- | --- | --- |
+| detect-secrets | 1.4.x | Secret detection | `detect-secrets scan --baseline .secrets.baseline` |
+| trivy | 0.56.x | Vulnerability scanning | `trivy fs --severity HIGH,CRITICAL .` |
+| semgrep | 1.94.x | Static analysis | `semgrep --config=auto --error .` |
+| bandit | 1.7.x | Python security | `bandit -r src/ -ll` |
+| npm audit | latest | JS dependencies | `npm audit --audit-level=high` |
+| gosec | 2.x | Go security | `gosec ./...` |
+
+**Security Checklist**:
+- No hardcoded secrets (API keys, passwords, tokens)
+- Input validation on all external data
+- Proper error handling (no sensitive info in errors)
+- Dependency vulnerability scan passed
+- Access control enforced
+- HTTPS/TLS for network calls
+
+### T - Trackable (TAG Chain Integrity)
+
+**TAG Structure Validation**:
+- `@SPEC:ID` in specs (`.moai/specs/SPEC-<ID>/spec.md`)
+- `@TEST:ID` in tests (`tests/`)
+- `@CODE:ID` in source (`src/`)
+- `@DOC:ID` in docs (`docs/`)
+
+**Chain Verification**:
+```bash
+# Scan all TAGs
+rg '@(SPEC|TEST|CODE|DOC):' -n .moai/specs/ tests/ src/ docs/
+
+# Detect orphans
+rg '@CODE:AUTH-001' -n src/          # CODE exists
+rg '@SPEC:AUTH-001' -n .moai/specs/  # SPEC missing → orphan
+```
 
-**T - Trackable**:
-- TAG chain integrity (@SPEC → @TEST → @CODE → @DOC)
+**Traceability Requirements**:
+- Every `@CODE:ID` must reference `@SPEC:ID` and `@TEST:ID`
+- TAG block includes file paths: `SPEC: <path> | TEST: <path>`
+- HISTORY section tracks all changes with dates
+- No duplicate TAG IDs across project
 
 ## Inputs
-- Project standard documents (e.g. `CLAUDE.md`, `.moai/config.json`).
-- Latest printouts from relevant sub-agents.
+- Project configuration (`.moai/config.json`, `CLAUDE.md`)
+- Source code (`src/`, `tests/`)
+- SPEC documents (`.moai/specs/`)
+- CI/CD configuration (`.github/workflows/`)
 
 ## Outputs
-- Templates or policy summaries conforming to the MoAI-ADK standard.
-- Reusable rules/checklists.
+- TRUST compliance report (pass/fail per principle)
+- Coverage metrics with delta from previous run
+- Security scan results
+- TAG chain validation report
+- Quality gate decision (block/allow merge)
+
+## CI/CD Integration
+
+**GitHub Actions Example** (`.github/workflows/trust-validation.yml`):
+
+```yaml
+name: TRUST Validation
+
+on: [pull_request, push]
+
+jobs:
+  trust-check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      # T - Test First (Python example)
+      - name: Run tests with coverage
+        run: |
+          pip install pytest pytest-cov
+          pytest --cov=src --cov-report=xml --cov-fail-under=85
+
+      # R - Readable
+      - name: Lint code
+        run: |
+          pip install ruff
+          ruff check .
+
+      # U - Unified
+      - name: Type check
+        run: |
+          pip install mypy
+          mypy src/ --strict
+
+      # S - Secured
+      - name: Security scan
+        uses: aquasecurity/trivy-action@master
+        with:
+          scan-type: 'fs'
+          severity: 'HIGH,CRITICAL'
+          exit-code: '1'
+
+      - name: Secret detection
+        run: |
+          pip install detect-secrets
+          detect-secrets scan --baseline .secrets.baseline
+
+      # T - Trackable
+      - name: TAG validation
+        run: |
+          # Check for orphaned TAGs
+          ./scripts/validate-tags.sh
+```
+
+## Quality Gate Enforcement
+
+**Merge Requirements**:
+- All 5 TRUST principles must pass
+- Test coverage ≥85% (no regression from baseline)
+- Zero high/critical security vulnerabilities
+- All TAGs have valid chains
+- Code review approved
+
+**Failure Actions**:
+- Block PR merge
+- Post detailed failure report as PR comment
+- Suggest remediation steps
+- Link to relevant documentation
 
 ## Failure Modes
-- When required standard files are missing or have limited access rights.
-- When conflicting policies are detected and coordination is required.
+- Missing standard files (`.moai/config.json`, `CLAUDE.md`)
+- Insufficient file access permissions
+- Conflicting policies requiring coordination
+- Tool version mismatches in CI vs local
+- Network failures during dependency scans
 
 ## Dependencies
-- There is great synergy when called together with cc-manager.
+- Works synergistically with `moai-foundation-tags` (TAG traceability)
+- Requires `moai-foundation-specs` (SPEC validation)
+- Integrates with `cc-manager` for session management
 
 ## References
+- pytest Documentation. "Coverage Reporting." https://docs.pytest.org/en/stable/how-to/coverage.html (accessed 2025-10-22).
+- Vitest Documentation. "Coverage Guide." https://vitest.dev/guide/coverage.html (accessed 2025-10-22).
+- Go Testing Package. "Coverage Testing." https://go.dev/blog/coverage (accessed 2025-10-22).
+- Trivy Documentation. "Vulnerability Scanning." https://trivy.dev/ (accessed 2025-10-22).
+- detect-secrets. "Secret Detection Tool." https://github.com/Yelp/detect-secrets (accessed 2025-10-22).
+- SemGrep. "Lightweight SAST." https://semgrep.dev/docs/ (accessed 2025-10-22).
 - SonarSource. "Quality Gate: Developer's Guide." https://www.sonarsource.com/company/newsroom/white-papers/quality-gate/ (accessed 2025-03-29).
 - ISO/IEC 25010. "Systems and software quality models." (accessed 2025-03-29).
 
 ## Changelog
-- 2025-03-29: Foundation skill templates have been enhanced to align with best practice structures.
+- 2025-10-22: v2.0.0 - Added latest tool versions (pytest 8.4.2, Vitest 2.0.5, trivy 0.56.x, etc.), CI/CD automation, SAST tools, quality gate enforcement
+- 2025-03-29: v1.0.0 - Foundation skill templates enhanced to align with best practice structures
 
 ## Works well with
 
-- moai-foundation-tags (TAG traceability)
-- moai-foundation-specs (SPEC validation)
+- `moai-foundation-tags` (TAG traceability)
+- `moai-foundation-specs` (SPEC validation)
+- `moai-alfred-trust-validation` (Alfred workflow integration)
+- `cc-manager` (session management)
 
 ## Examples
-```markdown
-- Scan standard documents and report missing sections.
-- Changed regulations are reflected in CLAUDE.md.
+
+**Scenario 1: Pre-merge TRUST validation**
+```bash
+# Run full TRUST check before merging
+pytest --cov=src --cov-fail-under=85
+ruff check .
+mypy src/ --strict
+trivy fs --severity HIGH,CRITICAL .
+detect-secrets scan
+rg '@(SPEC|TEST|CODE):' -n .moai/specs/ tests/ src/
+```
+
+**Scenario 2: CI/CD pipeline integration**
+```yaml
+# GitHub Actions workflow snippet
+- name: TRUST Gate
+  run: |
+    chmod +x scripts/trust-check.sh
+    ./scripts/trust-check.sh || exit 1
+```
+
+**Scenario 3: Local development pre-commit**
+```bash
+# .git/hooks/pre-commit
+#!/bin/bash
+pytest --cov=src --cov-fail-under=85 --quiet || exit 1
+ruff check . --quiet || exit 1
+mypy src/ --strict --no-error-summary || exit 1
 ```
 
 ## Best Practices
-- When changing standards, the reason for change and supporting documents are recorded.
-- Follow the single source principle and avoid modifying the same item in multiple places.
+- Run TRUST validation locally before pushing
+- Configure IDE to show coverage inline
+- Automate quality gates in CI/CD (never manual)
+- Track coverage trends over time
+- Document reasons for TRUST exceptions (with approval)
+- Update tool versions quarterly
+- Use pre-commit hooks for fast feedback
+- Fail fast on security violations
+- Generate coverage reports for review
+- Archive TRUST reports per release