Removed the references file

Author: cs-raj

.talismanrc

@@ -1,8 +1,11 @@
 fileignoreconfig:
   - filename: skills/dev-workflow/SKILL.md
     checksum: bbe23955b8865b7b44e8adaf414dce2b0127921ed1e35488adf470fdd833270f
-  - filename: skills/code-review/references/code-review-checklist.md
-    checksum: 7b5132bc27e2328f32ecf38941bb117a77be0d83502f15c3a5d1933f3220b6fc
   - filename: package-lock.json
     checksum: 31cf2fecced45ffd2db8b1f7c5258d1c98c2d0be7dd443460cfc070558a85c82
+  - filename: skills/contentstack-cli/SKILL.md
+    checksum: cd7046bfdace6bb82ff6168663f05b0a641e615d61167412d0a4c724c3d18209
+  - filename: skills/code-review/SKILL.md
+    checksum: f4fb9f63b97acf35845f31577840050af6c4f960dc6522477e31decc0b866313
+
 version: ""

skills/code-review/SKILL.md

@@ -16,7 +16,40 @@ description: PR and release checklist for cli-cm-regex-validate (security, packa
 
 Open [`skills/code-review/`](.) when reviewing PRs or before release (or point your agent at this folder if supported).
 
+## Checklist
+
+### Correctness and safety
+
+- [ ] Changes match the intended behavior for `cm:stacks:validate-regex` (flags, prompts, stack connection, CT/GF selection).
+- [ ] No API keys, management tokens, or secrets in code or tests; Talisman/Snyk hooks still make sense for local workflow.
+- [ ] New user-visible strings added to `messages/index.json` under `validateRegex` (avoid hard-coded copy in production paths).
+
+### Tests
+
+- [ ] `npm test` passes locally.
+- [ ] New behavior covered by `test/utils/` tests and/or `test/data/` fixtures where appropriate.
+- [ ] Mocks used for Management SDK and filesystem; no accidental live stack calls in unit tests.
+
+### Lint and types
+
+- [ ] ESLint passes (`posttest` or project eslint script). **Note:** CI does not run ESLint — only `npm test` in [`.github/workflows/unit-tests.yml`](../../.github/workflows/unit-tests.yml); lint must pass locally before merge.
+- [ ] TypeScript changes respect `strict` and project conventions (see `tsconfig.json`, `.eslintrc`, and [`AGENTS.md`](../../AGENTS.md)).
+
+### Packaging and release
+
+- [ ] `package.json` `files` includes what ships (`lib`, `bin`, `oclif.manifest.json`, `messages`, etc.).
+- [ ] `prepack` still runs `tsc`, `oclif manifest`, and `oclif readme` as needed for the plugin.
+- [ ] Version bumps follow team process; release workflow (e.g. push to `main`) matches `.github/workflows/release.yml` expectations.
+
+### CI / security workflows
+
+- [ ] Unit test workflow exercises `npm test` on a supported Node version (see `.github/workflows/unit-tests.yml`). Expect Jest only there — not `posttest`/ESLint unless you add a separate workflow.
+- [ ] SCA / policy workflows unchanged or intentionally updated; no silent downgrade of security checks.
+
+### Documentation
+
+- [ ] README or command examples updated if flags or behavior changed.
+
 ## References
 
-- [references/code-review-checklist.md](references/code-review-checklist.md)
 - [Development workflow](../dev-workflow/SKILL.md)

skills/code-review/references/code-review-checklist.md

@@ -18,8 +18,40 @@ description: Contentstack CLI plugin patterns for cm:stacks:validate-regex (SDK,
 
 Open [`skills/contentstack-cli/`](.) when changing commands, utils, or `messages/index.json` (or point your agent at this folder if supported).
 
+## Patterns (regex validation plugin)
+
+### Plugin identity
+
+- Package: `@contentstack/cli-cm-regex-validate`
+- Command id: `cm:stacks:validate-regex` (short name `RGXVLD` in `package.json` `csdxConfig` when present)
+- Entry: `src/commands/cm/stacks/validate-regex.ts`
+
+### End-to-end flow
+
+1. **Parse** — `this.parse(ValidateRegex)`; flags: `alias`, `contentType`, `globalField`, `filePath`, `help`.
+2. **Prompts** — If alias or module flags are missing, `inquireAlias` / `inquireModule` (`src/utils/interactive.ts`, Inquirer).
+3. **Token** — `this.getToken(alias)` from Contentstack CLI; errors use `messages.validateRegex.errors.tokenNotFound` and `ref` to docs.
+4. **Connect** — `connect-stack.ts`: `contentstackSdk.client({ host })`, optional `early_access` headers, `client.stack({ api_key, management_token })`.
+5. **Process** — `process-stack.ts`: for each selected module, `stack.contentType()` / `stack.globalField()` → `.query({}).find()`, then `safe-regex.ts` on each item.
+6. **Output** — `generate-output.ts`: `results.csv` via `jsonexport`, table via `cli-table3`, paths via `sanitizePath`; user copy from `messages/index.json`.
+
+### Schema traversal
+
+- Recurse into `schema` for `group` and `global_field`.
+- For `blocks`, iterate `blocks` and each block’s `schema`.
+- For each field with `format`, call `safe-regex`; collect module, title, UID, field metadata, and pattern for invalid rows.
+
+### User-facing strings
+
+- All strings live under `messages/index.json` → `validateRegex` (command, interactive, cliAction, errors, output).
+- Docs link in output points to Contentstack guidance on catastrophic backtracking / validation regex.
+
+### Related packages
+
+- `@contentstack/cli-command`, `@contentstack/cli-utilities`, `@contentstack/management`
+- `cli-ux` (spinner), `inquirer` (prompts), `safe-regex`, `jsonexport`, `cli-table3`
+
 ## References
 
-- [references/contentstack-patterns.md](references/contentstack-patterns.md)
 - [Development workflow](../dev-workflow/SKILL.md)
 - [Testing](../testing/SKILL.md)

skills/contentstack-cli/SKILL.md

@@ -19,7 +19,48 @@ description: Jest testing patterns for cli-cm-regex-validate (mocks, fixtures, n
 
 When using an agent or IDE that supports folder context, open [`skills/testing/`](.) for test-focused guidance.
 
+## Patterns (Jest)
+
+This project uses **Jest** and **ts-jest**. **`npm test`** (Jest) is the canonical test command; CI runs `npm test` from `.github/workflows/unit-tests.yml`. The `mocha` script in `package.json` is **not** what CI runs—do not use `npm run mocha` as the project test entry point.
+
+### File layout
+
+| Area | Path |
+|------|------|
+| Tests | `test/utils/*.test.ts` |
+| Fixtures | `test/data/*.json` |
+
+Mirror utility names where it helps (`connect-stack.test.ts` vs `connect-stack.ts`).
+
+### Commands
+
+- `npm test` — runs Jest with `jest.config.ts` (roots, `testMatch`, ts-jest transform, coverage).
+
+### Mocking
+
+- **Management SDK:** `jest.mock('@contentstack/management')` and stub `client`, `stack`, and query chains as in `connect-stack.test.ts`.
+- **Filesystem:** `jest.mock('fs')` when testing CSV path creation and `writeFileSync` / `mkdirSync`.
+- **cli-ux:** mock `cli.action.start` / `stop` when asserting spinner behavior; avoid reassigning imported bindings with `@ts-ignore`—prefer `jest.mock('cli-ux', () => ({ ... }))` when needed.
+- **cli-utilities:** mock `cliux.print` and `sanitizePath` in output tests when asserting printed messages and paths.
+
+### Fixtures
+
+- Load JSON with `require('../data/...')` for content type / global field documents and expected invalid-regex rows.
+- Keeps tests readable and matches real API shape (schema, `data_type`, `format`, nested `group` / `blocks`).
+
+### Assertions
+
+- Use `toHaveBeenCalled`, `toHaveBeenCalledWith`, `toStrictEqual` for objects and arrays.
+- Avoid deprecated matchers removed in newer Jest (e.g. prefer `toHaveBeenCalled` over legacy aliases).
+
+### Async tests
+
+- Use `async`/`await` for utilities that return promises; await `inquireAlias` / `inquireModule` when testing interactive flows with mocked `inquirer`.
+
+### Note on `package.json`
+
+- This repo lists **`jest`** under **`dependencies`** in `package.json`. Run tests via **`npm test`** and describe the framework as Jest in documentation and for agents.
+
 ## References
 
-- [references/testing-patterns.md](references/testing-patterns.md)
 - [Development workflow](../dev-workflow/SKILL.md)