@jakkrichm/create-nexus-devflow 2.0.0

package/template/.agents/skills/changelog/SKILL.md

@@ -0,0 +1,109 @@
+---name: changelog
+
+description: Update CHANGELOG.md - Automatically gather changes from specs, git history, or current state to update the project changelog.
+---
+# Phase 53: Update Changelog
+
+This command automates the process of maintaining the `CHANGELOG.md` file by analyzing task specifications, git diffs, and the current project state.
+
+Primary behavior now lives in:
+
+```text
+.agents/skills/release-git-operations/SKILL.md
+```
+
+Treat this workflow file as a compatibility wrapper around that skill in `changelog` mode.
+
+## Usage
+
+Run the command by typing:
+```
+Changelog
+```
+
+## Objectives
+
+1.  **Change Detection**: Identify new features, fixes, and changes since the last recorded version in `CHANGELOG.md`.
+2.  **Automated Versioning**: Analyze the impact of changes to automatically select the next version number (Major, Minor, or Patch) based on Semantic Versioning (SemVer) principles.
+3.  **Source Analysis**:
+    *   Scan `devflow/` for `20-spec.md` files of active or recently completed tasks.
+    *   Check `git status` and `git diff` for uncommitted/staged changes.
+    *   Check `git log` if git is initialized to see history since the last tag or version entry.
+3.  **Automatic Formatting**: Generate a standardized changelog entry following the [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format.
+4.  **Consistency**: Ensure the `CHANGELOG.md` reflects the actual work done in the repository.
+
+## Process
+
+### 1. Version Detection & Setup
+1.  **Read Current Changelog**: Extract the latest version and date from `CHANGELOG.md`.
+2.  **Analyze & Determine Next Version**: 
+    *   Analyze the collected changes to decide the increment based on **Semantic Versioning (SemVer)**:
+        - **Major (+1.0.0)**: Use if there are breaking changes, [DELETE] operations on core modules, or major architectural shifts.
+        - **Minor (0.+1.0)**: Use if new features ([NEW]) or significant compatible additions are found.
+        - **Patch (0.0.+1)**: Use for bug fixes ([FIXED]), small tweaks ([MODIFY]), or documentation updates.
+    *   Auto-propose the version based on the highest impact category found.
+3.  **Get Current Date**: Use the current system date (YYYY-MM-DD).
+
+### 2. Information Gathering
+1.  **Scan devflow/**:
+    *   Find all `20-spec.md` files in subdirectories of `devflow/`.
+    *   Extract the `Goal` or `Requirements` sections to identify high-level features/fixes.
+2.  **Git Analysis** (if available):
+    *   Run `git status` to see current work in progress.
+    *   Run `git diff` to understand technical changes and impact.
+    *   Look for "BREAKING CHANGE" in git commit messages.
+3.  **Categorization & Impact Assessment**: Group findings and assess impact:
+    *   `Added` โ†’ Usually Minor.
+    *   `Changed` โ†’ Minor or Patch (Major if breaking).
+    *   `Fixed` โ†’ Patch.
+    *   `Removed` โ†’ Major (if public API/Core).
+    *   `Security` โ†’ Patch or Minor.
+
+### 3. Update CHANGELOG.md
+1.  **Template Verification**: Before generating a new changelog block, inspect `.agent/resources/schemas/changelog_entry.template.md`, use its headings, and manually apply the same no-placeholder gate to the inserted changelog block.
+2.  **Generate Entry**: Format the gathered information into a Markdown block.
+3.  **Insertion**: Use `replace_file_content` to insert the new version block at the top of the version list (usually after the header and description).
+4.  **Validation**: Ensure the file remains readable and correctly formatted.
+
+## Benefits
+- **Automation**: Reduces the manual effort of tracking changes.
+- **Accuracy**: Ensures all tasks documented in `devflow/` are captured.
+- **Standardization**: Maintains a consistent look and feel for project history.
+
+## System Prompt / Persona
+- **Release Engineer**: Focuses on clear, concise, and accurate documentation of software changes.
+- **Technical Writer**: Ensures the changelog is readable for both humans and machines.
+
+## Insight Addon
+
+When recent work includes useful lessons, apply the `insight_extractor` pattern before writing the changelog:
+
+- Extract reusable patterns, gotchas, and file insights from task artifacts and git diff.
+- Keep lessons actionable and concise.
+- Include only user-facing changes in `CHANGELOG.md`; keep internal gotchas in `devflow/lessons.md` or task logs.
+
+## Management-Talk Addon
+
+When changelog input is too implementation-heavy, apply `.agents/skills/9arm-skills/management-talk/SKILL.md` as a credited communication lens:
+
+- Source pack: `9arm-skills`
+- Credit: `thananon/9arm-skills`
+- Adapted for: Antigravity IDE / Nexus-DevFlow
+- Preserve user-facing impact, validation, risk, and follow-up.
+- Remove low-value internal details such as function names, long file paths, and commit SHAs unless they are needed for release decisions.
+
+## Relationship To DevFlow 2.0
+
+- Classification: Companion command
+- Mainline status: Release communication support, not a numbered stage
+- Typical entry points: `/70-Release`, `Deploy`, `PR`
+- Typical handoff targets: `/60-Report`, `Wiki`
+
+## Sources
+
+- `AGENTS.md`
+- `.agents/skills/release-git-operations/SKILL.md`
+- `.agent/resources/schemas/changelog_entry.template.md`
+- Related commands: `/70-Release`, `Deploy`, `PR`, `/60-Report`, `Wiki`
+
+

package/template/.agents/skills/check-for-updates/SKILL.md

@@ -0,0 +1,117 @@
+---name: check-for-updates
+
+description: Install, upgrade, or verify Nexus-DevFlow setup for this machine or project using SETUP-BY-AI.md as the source of truth.
+argument-hint: [optional: target project path, provider/tool, or update intent]
+---
+
+# Check For Updates
+
+`Check-For-Updates` is a public companion command for Nexus-DevFlow install, upgrade, and setup verification work.
+
+It is not a numbered mainline stage.
+
+## Mission
+
+Install or upgrade Nexus-DevFlow 2.0 for this machine or target project.
+
+First read `SETUP-BY-AI.md` from the Nexus-DevFlow repository and use it as the operational source of truth.
+
+Detect:
+
+- framework root
+- package version
+- provider or tool
+- target project
+- whether the current setup is using `Codex global`, `Central clone + link`, or `Manual copy / overwrite`
+
+Keep `.workspaces` project-local.
+
+Do not overwrite user instruction files blindly.
+
+After install or upgrade, run `roadmap:validate`, `validate`, and `validate:all` where relevant, then report files changed, installed version, framework root, chosen route, and any manual approval steps.
+
+Repository reference:
+
+```text
+https://github.com/Jakkrich/nexus-devflow
+```
+
+## When To Use
+
+Use this command when:
+
+- the user wants to install Nexus-DevFlow into Codex or another AI tool
+- the user wants to install Nexus-DevFlow into a target project
+- the user wants to upgrade an existing Nexus-DevFlow install
+- the user wants to check whether the current machine or project is on the expected framework version
+- the user needs routing across optional Codex global setup, `Central clone + link`, or `Manual copy / overwrite`
+
+## Operating Rules
+
+- `SETUP-BY-AI.md` is the operational source of truth
+- prefer the safest route that matches the user request and existing environment
+- for project-local setup, prefer `Central clone + link`
+- use `Manual copy / overwrite` only when linking is unsuitable or explicitly rejected
+- treat `AI install` as guided execution of one of the supported routes, not as a separate bundle layout
+- preserve user-authored instructions outside managed Nexus-DevFlow content
+- do not link, copy, or share `.workspaces` from the framework repo into another project
+- if the framework repo is dirty, do not pull automatically; report the dirty files and ask before proceeding with a pull-based update
+- do not claim success until the relevant validation commands pass
+
+## Execution Flow
+
+1. Read `SETUP-BY-AI.md`.
+2. Detect the framework root and confirm the framework files listed there exist.
+3. Detect the installed or target version from `package.json`.
+4. Detect the provider or tool context.
+5. Detect the target project and keep its `.workspaces` local to that project.
+6. Detect the current route already in use, if any:
+   - optional `Codex global`
+   - `Central clone + link`
+   - `Manual copy / overwrite`
+7. Choose the route:
+   - optional `Codex global` only when explicitly requested
+   - `Central clone + link` for project-local setup by default
+   - `Manual copy / overwrite` only when linking is not suitable
+8. If upgrading and the user wants latest, inspect git cleanliness before any pull-based update.
+9. Apply the relevant install or upgrade commands.
+10. Run validation:
+   - `npm.cmd run roadmap:validate`
+   - `npm.cmd run validate`
+   - `npm.cmd run validate:all`
+   - plus provider-specific checks such as `npm.cmd run codex:check-global` when applicable
+11. Report the outcome in the final setup result format.
+
+## Final Report Format
+
+```text
+Nexus-DevFlow setup result
+- Mode:
+- Framework root:
+- Framework version:
+- Target project:
+- Provider:
+- Files changed:
+- Validation:
+- Warnings or manual steps:
+```
+
+## Relationship To DevFlow 2.0
+
+- Classification: Companion command
+- Mainline status: Not a numbered stage
+- Typical entry points: before using DevFlow on a new machine, before linking or copying into a target project, after pulling framework changes, or during provider setup maintenance
+- Typical handoff targets: `Help`, `/00-Discover`, or the user's requested active task after setup is verified
+
+## Sources
+
+- `SETUP-BY-AI.md`
+- `SETUP.md`
+- `AGENTS.md`
+- `package.json`
+- `docs/install-update-troubleshooting.md`
+
+## Next Workflow Recommendation
+
+- Default: return to the user's requested work after setup is verified
+- Common routes: `Help` for routing, `/00-Discover` for new work, or `/50-Verify` when setup validation exposes framework issues

package/template/.agents/skills/ci-cd-and-automation/SKILL.md

@@ -0,0 +1,390 @@
+---
+name: ci-cd-and-automation
+description: Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
+---
+
+# CI/CD and Automation
+
+## Overview
+
+Automate quality gates so that no change reaches production without passing tests, lint, type checking, and build. CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss, and it does so consistently on every single change.
+
+**Shift Left:** Catch problems as early in the pipeline as possible. A bug caught in linting costs minutes; the same bug caught in production costs hours. Move checks upstream — static analysis before tests, tests before staging, staging before production.
+
+**Faster is Safer:** Smaller batches and more frequent releases reduce risk, not increase it. A deployment with 3 changes is easier to debug than one with 30. Frequent releases build confidence in the release process itself.
+
+## When to Use
+
+- Setting up a new project's CI pipeline
+- Adding or modifying automated checks
+- Configuring deployment pipelines
+- When a change should trigger automated verification
+- Debugging CI failures
+
+## The Quality Gate Pipeline
+
+Every change goes through these gates before merge:
+
+```
+Pull Request Opened
+    │
+    ▼
+┌─────────────────┐
+│   LINT CHECK     │  eslint, prettier
+│   ↓ pass         │
+│   TYPE CHECK     │  tsc --noEmit
+│   ↓ pass         │
+│   UNIT TESTS     │  jest/vitest
+│   ↓ pass         │
+│   BUILD          │  npm run build
+│   ↓ pass         │
+│   INTEGRATION    │  API/DB tests
+│   ↓ pass         │
+│   E2E (optional) │  Playwright/Cypress
+│   ↓ pass         │
+│   SECURITY AUDIT │  npm audit
+│   ↓ pass         │
+│   BUNDLE SIZE    │  bundlesize check
+└─────────────────┘
+    │
+    ▼
+  Ready for review
+```
+
+**No gate can be skipped.** If lint fails, fix lint — don't disable the rule. If a test fails, fix the code — don't skip the test.
+
+## GitHub Actions Configuration
+
+### Basic CI Pipeline
+
+```yaml
+# .github/workflows/ci.yml
+name: CI
+
+on:
+  pull_request:
+    branches: [main]
+  push:
+    branches: [main]
+
+jobs:
+  quality:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Lint
+        run: npm run lint
+
+      - name: Type check
+        run: npx tsc --noEmit
+
+      - name: Test
+        run: npm test -- --coverage
+
+      - name: Build
+        run: npm run build
+
+      - name: Security audit
+        run: npm audit --audit-level=high
+```
+
+### With Database Integration Tests
+
+```yaml
+  integration:
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: postgres:16
+        env:
+          POSTGRES_DB: testdb
+          POSTGRES_USER: ci_user
+          POSTGRES_PASSWORD: ${{ secrets.CI_DB_PASSWORD }}
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          cache: 'npm'
+      - run: npm ci
+      - name: Run migrations
+        run: npx prisma migrate deploy
+        env:
+          DATABASE_URL: postgresql://ci_user:${{ secrets.CI_DB_PASSWORD }}@localhost:5432/testdb
+      - name: Integration tests
+        run: npm run test:integration
+        env:
+          DATABASE_URL: postgresql://ci_user:${{ secrets.CI_DB_PASSWORD }}@localhost:5432/testdb
+```
+
+> **Note:** Even for CI-only test databases, use GitHub Secrets for credentials rather than hardcoding values. This builds good habits and prevents accidental reuse of test credentials in other contexts.
+
+### E2E Tests
+
+```yaml
+  e2e:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '22'
+          cache: 'npm'
+      - run: npm ci
+      - name: Install Playwright
+        run: npx playwright install --with-deps chromium
+      - name: Build
+        run: npm run build
+      - name: Run E2E tests
+        run: npx playwright test
+      - uses: actions/upload-artifact@v4
+        if: failure()
+        with:
+          name: playwright-report
+          path: playwright-report/
+```
+
+## Feeding CI Failures Back to Agents
+
+The power of CI with AI agents is the feedback loop. When CI fails:
+
+```
+CI fails
+    │
+    ▼
+Copy the failure output
+    │
+    ▼
+Feed it to the agent:
+"The CI pipeline failed with this error:
+[paste specific error]
+Fix the issue and verify locally before pushing again."
+    │
+    ▼
+Agent fixes → pushes → CI runs again
+```
+
+**Key patterns:**
+
+```
+Lint failure → Agent runs `npm run lint --fix` and commits
+Type error  → Agent reads the error location and fixes the type
+Test failure → Agent follows debugging-and-error-recovery skill
+Build error → Agent checks config and dependencies
+```
+
+## Deployment Strategies
+
+### Preview Deployments
+
+Every PR gets a preview deployment for manual testing:
+
+```yaml
+# Deploy preview on PR (Vercel/Netlify/etc.)
+deploy-preview:
+  runs-on: ubuntu-latest
+  if: github.event_name == 'pull_request'
+  steps:
+    - uses: actions/checkout@v4
+    - name: Deploy preview
+      run: npx vercel --token=${{ secrets.VERCEL_TOKEN }}
+```
+
+### Feature Flags
+
+Feature flags decouple deployment from release. Deploy incomplete or risky features behind flags so you can:
+
+- **Ship code without enabling it.** Merge to main early, enable when ready.
+- **Roll back without redeploying.** Disable the flag instead of reverting code.
+- **Canary new features.** Enable for 1% of users, then 10%, then 100%.
+- **Run A/B tests.** Compare behavior with and without the feature.
+
+```typescript
+// Simple feature flag pattern
+if (featureFlags.isEnabled('new-checkout-flow', { userId })) {
+  return renderNewCheckout();
+}
+return renderLegacyCheckout();
+```
+
+**Flag lifecycle:** Create → Enable for testing → Canary → Full rollout → Remove the flag and dead code. Flags that live forever become technical debt — set a cleanup date when you create them.
+
+### Staged Rollouts
+
+```
+PR merged to main
+    │
+    ▼
+  Staging deployment (auto)
+    │ Manual verification
+    ▼
+  Production deployment (manual trigger or auto after staging)
+    │
+    ▼
+  Monitor for errors (15-minute window)
+    │
+    ├── Errors detected → Rollback
+    └── Clean → Done
+```
+
+### Rollback Plan
+
+Every deployment should be reversible:
+
+```yaml
+# Manual rollback workflow
+name: Rollback
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: 'Version to rollback to'
+        required: true
+
+jobs:
+  rollback:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Rollback deployment
+        run: |
+          # Deploy the specified previous version
+          npx vercel rollback ${{ inputs.version }}
+```
+
+## Environment Management
+
+```
+.env.example       → Committed (template for developers)
+.env                → NOT committed (local development)
+.env.test           → Committed (test environment, no real secrets)
+CI secrets          → Stored in GitHub Secrets / vault
+Production secrets  → Stored in deployment platform / vault
+```
+
+CI should never have production secrets. Use separate secrets for CI testing.
+
+## Automation Beyond CI
+
+### Dependabot / Renovate
+
+```yaml
+# .github/dependabot.yml
+version: 2
+updates:
+  - package-ecosystem: npm
+    directory: /
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+```
+
+### Build Cop Role
+
+Designate someone responsible for keeping CI green. When the build breaks, the Build Cop's job is to fix or revert — not the person whose change caused the break. This prevents broken builds from accumulating while everyone assumes someone else will fix it.
+
+### PR Checks
+
+- **Required reviews:** At least 1 approval before merge
+- **Required status checks:** CI must pass before merge
+- **Branch protection:** No force-pushes to main
+- **Auto-merge:** If all checks pass and approved, merge automatically
+
+## CI Optimization
+
+When the pipeline exceeds 10 minutes, apply these strategies in order of impact:
+
+```
+Slow CI pipeline?
+├── Cache dependencies
+│   └── Use actions/cache or setup-node cache option for node_modules
+├── Run jobs in parallel
+│   └── Split lint, typecheck, test, build into separate parallel jobs
+├── Only run what changed
+│   └── Use path filters to skip unrelated jobs (e.g., skip e2e for docs-only PRs)
+├── Use matrix builds
+│   └── Shard test suites across multiple runners
+├── Optimize the test suite
+│   └── Remove slow tests from the critical path, run them on a schedule instead
+└── Use larger runners
+    └── GitHub-hosted larger runners or self-hosted for CPU-heavy builds
+```
+
+**Example: caching and parallelism**
+```yaml
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with: { node-version: '22', cache: 'npm' }
+      - run: npm ci
+      - run: npm run lint
+
+  typecheck:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with: { node-version: '22', cache: 'npm' }
+      - run: npm ci
+      - run: npx tsc --noEmit
+
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with: { node-version: '22', cache: 'npm' }
+      - run: npm ci
+      - run: npm test -- --coverage
+```
+
+## Common Rationalizations
+
+| Rationalization | Reality |
+|---|---|
+| "CI is too slow" | Optimize the pipeline (see CI Optimization below), don't skip it. A 5-minute pipeline prevents hours of debugging. |
+| "This change is trivial, skip CI" | Trivial changes break builds. CI is fast for trivial changes anyway. |
+| "The test is flaky, just re-run" | Flaky tests mask real bugs and waste everyone's time. Fix the flakiness. |
+| "We'll add CI later" | Projects without CI accumulate broken states. Set it up on day one. |
+| "Manual testing is enough" | Manual testing doesn't scale and isn't repeatable. Automate what you can. |
+
+## Red Flags
+
+- No CI pipeline in the project
+- CI failures ignored or silenced
+- Tests disabled in CI to make the pipeline pass
+- Production deploys without staging verification
+- No rollback mechanism
+- Secrets stored in code or CI config files (not secrets manager)
+- Long CI times with no optimization effort
+
+## Verification
+
+After setting up or modifying CI:
+
+- [ ] All quality gates are present (lint, types, tests, build, audit)
+- [ ] Pipeline runs on every PR and push to main
+- [ ] Failures block merge (branch protection configured)
+- [ ] CI results feed back into the development loop
+- [ ] Secrets are stored in the secrets manager, not in code
+- [ ] Deployment has a rollback mechanism
+- [ ] Pipeline runs in under 10 minutes for the test suite