@danmoisan/drm-copilot-mcp 0.0.1 → 0.0.6

package/resources/codex-and-agents-customizations/.agents/skills/powershell-change-budget-router/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: powershell-change-budget-router
 description: Budget-first routing contract for PowerShell work: estimate production-file scope, choose small vs large path, enforce direct-mode escalation to orchestrator, and use the VS Code extension command surface for promotion lifecycle steps when available.
@@ -29,7 +24,7 @@ Use this skill when:
 ## Orchestrated Small-Path Requirements
 
 When routed through `powershell-orchestrator`, small path still requires lifecycle scaffolding before implementation:
-- invoke promotion/folder lifecycle steps through `vscode/runCommand` + extension access per `feature-promotion-lifecycle` when available; use script/CLI fallback only when direct extension command execution is unavailable,
+- invoke promotion/folder lifecycle steps through the `drm-copilot` MCP tools required by `repo-automation-adapter`. If the MCP server or required tool is unavailable, stop before promotion,
 - promote potential item to GitHub issue with `--work-mode minor-audit`,
 - create active feature folder with `--work-mode minor-audit`,
 - delegate minimal-audit plan creation to `atomic_planner` with `DIRECTIVE: MINIMAL-AUDIT PLAN REQUIRED`,

package/resources/codex-and-agents-customizations/.agents/skills/powershell-orchestration-state-machine/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: powershell-orchestration-state-machine
 description: Checkpoint schema and resume protocol for long-running PowerShell orchestration workflows.

package/resources/codex-and-agents-customizations/.agents/skills/powershell-qa-gate/SKILL.md

@@ -1,9 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- Rewrite Claude skill paths to shared skill paths.
-- Rewrite Claude rule paths to shared skill paths.
-
 ---
 name: powershell-qa-gate
 description: Final QA gate for PowerShell changes. Executes the full PoshQC format -> analyze -> test toolchain (with coverage where enforced), compares against a captured baseline, enforces zero-regression deltas, and produces the required reporting block before the agent declares the change complete.
@@ -33,9 +27,9 @@ Before invoking this gate, the agent must have:
 
 Run the full toolchain in this exact order. If any step fails or modifies files, fix the issue and restart from step 1. Do not stop the loop until all steps complete without errors in a single pass.
 
-1. `mcp__drmCopilotExtension__run_poshqc_format`
-2. `mcp__drmCopilotExtension__run_poshqc_analyze`
-3. `mcp__drmCopilotExtension__run_poshqc_test`
+1. `mcp__drm-copilot__run_poshqc_format`
+2. `mcp__drm-copilot__run_poshqc_analyze`
+3. `mcp__drm-copilot__run_poshqc_test`
 4. Coverage check (when enforced by task/repo flow) — use the Pester coverage output from step 3 or the repo coverage task.
 
 If the environment prevents running any tool, stop and report the change as **unverified**. Do not declare completion.

package/resources/codex-and-agents-customizations/.agents/skills/pr-author/SKILL.md

@@ -1,14 +1,6 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: pr-author
 description: Write a GitHub-ready pull request body from the canonical PR-context bundle with strict verification and auto-close rules.
-allowed-tools:
-  - Read
-  - "Bash(git log *)"
 ---
 
 # PR Author Skill
@@ -52,4 +44,4 @@ Use these sections in this order:
 - Only mention an issue/PR number if it appears verbatim in the provided context.
 - Do not treat PR numbers as issues.
 - Auto-close bullets must use exactly `- Closes #NNN` format, sourced only from "Issues to autoclose" or "Author-asserted autoclose issues."
-- If GitHub validation is unavailable/unverified, do not emit `Closes`; use the fallback `None` bullet.
+- If GitHub validation is unavailable or unverified, do not emit `Closes`; use the `None` bullet.

package/resources/codex-and-agents-customizations/.agents/skills/pr-base-branch-merge-base/SKILL.md

@@ -1,11 +1,6 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: pr-base-branch-merge-base
-description: 'Resolve PRBaseBranch for mcp__drmCopilotExtension__collect_pr_context using merge-base ancestry. Use when orchestrators or review workflows need the correct comparison base branch and must select the branch with the most recent common ancestor commit with HEAD.'
+description: 'Resolve PRBaseBranch for mcp__drm-copilot__collect_pr_context using merge-base ancestry. Use when orchestrators or review workflows need the correct comparison base branch and must select the branch with the most recent common ancestor commit with HEAD.'
 ---
 
 # PR Base Branch (Merge-Base)
@@ -15,7 +10,7 @@ Deterministic branch-selection rules for PR context collection.
 ## When to Use This Skill
 
 Use this skill when:
-- running `mcp__drmCopilotExtension__collect_pr_context`,
+- running `mcp__drm-copilot__collect_pr_context`,
 - delegating post-implementation review that depends on `PRBaseBranch`,
 - constructing PR context artifacts where the base must not be hard-coded.
 
@@ -42,14 +37,14 @@ Definition of correct base:
 ## Guardrails
 
 - Do not default to `main` unless merge-base resolution fails for all candidates.
-- If all candidates fail, surface explicit error context and use repository default branch only as last-resort fallback.
+- If all candidates fail, surface explicit error context and stop unless repository metadata directly identifies the default branch.
 - Persist chosen `PRBaseBranch` in orchestration state and reuse it within the same run.
 
 ## Collector Invocation Rule
 
 When invoking PR context collection, pass the resolved base explicitly:
 
-- `mcp__drmCopilotExtension__collect_pr_context` with `base=<resolved-PRBaseBranch>`
+- `mcp__drm-copilot__collect_pr_context` with `base=<resolved-PRBaseBranch>`
 
 ## Evidence Recommendation
 

package/resources/codex-and-agents-customizations/.agents/skills/pr-context-artifacts/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: pr-context-artifacts
 description: 'PR context artifact locations and refresh rules. Use when generating, reading, or inlining pr_context summary/appendix artifacts.'

package/resources/codex-and-agents-customizations/.agents/skills/python/SKILL.md

@@ -1,9 +1,5 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
+name: python
 paths:
   - "**/*.py"
 description: Python-specific toolchain and coding standards.

package/resources/codex-and-agents-customizations/.agents/skills/python-change-budget-router/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: python-change-budget-router
 description: Budget-first routing and batch-scope contract for Python work. Estimate production-file scope, choose small vs large path, enforce the 3 production + 3 test per-batch cap, and halt the agent for scope expansion approval when the estimate exceeds the budget.
@@ -64,7 +59,7 @@ If `python-typed-engineer` is invoked directly and estimated scope is `>3` produ
 
 When routed through the orchestrator, the small path still requires lifecycle scaffolding before implementation:
 
-- invoke promotion and folder lifecycle steps through `vscode/runCommand` and extension access per `feature-promotion-lifecycle` when available. Use script or CLI fallback only when direct extension command execution is unavailable.
+- invoke promotion and folder lifecycle steps through the `drm-copilot` MCP tools required by `repo-automation-adapter`. If the MCP server or required tool is unavailable, stop before promotion.
 - promote the potential item to a GitHub issue with `--work-mode minor-audit`,
 - create the active feature folder with `--work-mode minor-audit`,
 - delegate minimal-audit plan creation to `atomic_planner` with `DIRECTIVE: MINIMAL-AUDIT PLAN REQUIRED`,

package/resources/codex-and-agents-customizations/.agents/skills/python-qa-gate/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- Rewrite Claude skill paths to shared skill paths.
-
 ---
 name: python-qa-gate
 description: Final QA gate for Python changes. Executes the full Black -> Ruff -> Pyright -> Pytest toolchain, compares against a captured baseline, enforces zero-regression deltas, and produces the required reporting block before the agent declares the change complete.

package/resources/codex-and-agents-customizations/.agents/skills/python-suppressions/SKILL.md

@@ -1,12 +1,8 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
+name: python-suppressions
 paths:
   - "**/*.py"
-description: Pre-authorized Python Ruff and Pyright suppression patterns. Applies to Python files.
+description: Python suppression policy for linting and type-checking exceptions.
 ---
 
 # Python Suppression Policy

package/resources/codex-and-agents-customizations/.agents/skills/quality-tiers/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: quality-tiers
+description: Module rigor tier system and uniform coverage thresholds.
+paths:
+  - "**"
+description: Module rigor tier system and uniform coverage thresholds.
+---
+
+# Converted rule
+
+Source: legacy Claude rule `quality-tiers`.
+
+# Module Rigor Tiers
+
+This rule defines the T1–T4 module rigor tier system used by all CI gates in this repository. The tier system source of truth is `docs/ci.research.md` section 1; the file `quality-tiers.yml` at the repository root maps every project to a tier. Adding a project without a tier classification fails CI.
+
+## Tiers
+
+- **T1 — Critical.** Behavior bugs cause silent data loss, model drift, or security holes. Examples (No-COM architecture): classifier engines (SpamBayes, Triage), ToDo ID allocator and hierarchy operations, Graph extended-properties adapter, auth/token handling, host-agnostic command bus.
+- **T2 — Core.** Bugs cause feature regressions but not data loss. Examples: `TaskMaster.Domain`, `TaskMaster.Application`, mail-item DTOs, settings store abstraction, schema definitions.
+- **T3 — Adapters & UI.** Glue around APIs the team does not own. Examples: Outlook task pane UI, Office.js wrappers, Microsoft Graph SDK wrappers, persistence I/O.
+- **T4 — Scaffolding.** Examples: DI wiring, bootstrap, build scripts, dev tooling, generated code, manifests.
+
+## Source of Truth
+
+- `quality-tiers.yml` at repo root maps every project to one tier.
+- The CI pipeline's `tier-classification` stage validates that every project entry has a tier and that no unclassified project exists. Adding a project without a tier classification fails CI.
+
+## Uniform-vs-Tier-Dependent Gate Matrix
+
+Per Authoritative Decision #2, line and branch coverage thresholds are uniform across all tiers. Other gates remain tier-dependent.
+
+### Uniform across all tiers (T1–T4)
+
+- Format check: 100% pass.
+- Lint errors: 0.
+- Type errors: 0.
+- Architecture violations: 0.
+- Line coverage: >= 85%.
+- Branch coverage: >= 75%.
+- No regression on changed lines.
+
+### Tier-dependent
+
+| Gate | T1 | T2 | T3 | T4 |
+|---|---|---|---|---|
+| Untyped escape hatches (`any`/`dynamic`) | 0 | 0 | <= 5 per file, justified | unlimited |
+| Property test density | >= 1 per pure function | >= 1 per pure function | none | none |
+| Mutation score | >= 75% | trend-only | none | none |
+| Contract breaking changes | major bump required | major bump required | n/a | n/a |
+| Determinism (retry rate) | < 0.5% | < 1% | < 2% | n/a |
+| Golden tests | required for classifier-output modules | optional | none | none |
+| Full E2E suite scope | all critical paths | core paths | adapter smoke | none |
+
+## Rationale (uniform coverage thresholds)
+
+High test coverage is a fundamental quality-control design choice that enables autonomous agentic development and trust in the work product. For that reason, line coverage >= 85% and branch coverage >= 75% apply uniformly across T1–T4; tier-specific lower coverage floors are not used in this repository.

package/resources/codex-and-agents-customizations/.agents/skills/remediation-handoff-atomic-planner/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: remediation-handoff-atomic-planner
 description: 'Reusable remediation trigger and atomic_planner handoff steps. Use when audits require remediation inputs and a delegated remediation plan.'

package/resources/codex-and-agents-customizations/.agents/skills/repo-automation-adapter/SKILL.md

@@ -1,49 +1,39 @@
 ---
 name: repo-automation-adapter
-description: 'Centralize host-surface and repo-automation differences for Codex. Use when a migrated workflow previously depended on GitHub Copilot or VS Code extension commands and needs a single Codex-compatible execution or fallback rule.'
+description: 'Centralize required drm-copilot MCP execution for Codex repo automation. Use when a workflow needs promotion, PR context, commit context, customization publishing, hard-lock resolution, or orchestration validation.'
 ---
 
 # Repo Automation Adapter
 
-Use this skill to keep host-specific workflow translation in one place.
+Use this skill to keep host-specific workflow execution rules in one place.
 
-## When to Use This Skill
+## Canonical Rule
 
-Use this skill when:
-- a migrated skill previously depended on `drmCopilotExtension.*` commands,
-- a workflow needs PR-context collection, issue promotion, or feature-folder creation,
-- the same fallback behavior would otherwise be repeated across multiple skills.
+The `drm-copilot` MCP server is the only approved execution surface for canonical repository automation covered by this skill.
 
-## Canonical Rule
+There is no fallback. If the server is unavailable, the required tool is unavailable, or the MCP call fails, the workflow must stop, persist blocked state when an orchestrator checkpoint is active, and report the missing dependency or failed MCP operation.
 
-Do not encode host-specific execution details in multiple workflow skills. Put them here and have the calling skills reference this skill.
+Do not replace a required MCP operation with local scripts, git reconstruction, direct filesystem synthesis, VS Code command IDs, or best-effort behavior.
 
-## Published Codex Automation Surface
+## When to Use This Skill
 
-The canonical Codex automation dependency for this repo is the published MCP server:
-- `drmCopilotExtension`
+Use this skill when:
 
-Downstream Codex skills should depend on the MCP server name `drmCopilotExtension`, not on raw VS Code command IDs.
+- a migrated workflow previously depended on `drmCopilotExtension.*` commands,
+- a workflow needs PR-context collection, issue promotion, feature-folder creation, commit-context collection, customization publishing, hard-lock prompt resolution, or orchestration-artifact validation,
+- multiple skills need the same MCP-required execution rule.
 
-Declare that dependency once on this skill via `agents/openai.yaml`.
+## Published Codex Automation Surface
 
-## Codex Capability Model
+The required Codex automation dependency for this repo is the published MCP server:
 
-Codex in this repo can reliably use:
-- repository files,
-- shell commands,
-- git,
-- local scripts that already exist in the repository,
-- configured MCP tools when available.
+- `drm-copilot`
 
-Codex in this repo should not assume direct access to:
-- `vscode/runCommand`,
-- `drmCopilotExtension.*` command execution,
-- GitHub issue or PR mutation unless an explicit connector or script is available.
+Downstream Codex skills must depend on the MCP server name `drm-copilot`, not on raw VS Code command IDs.
 
 ## Published MCP Tool Surface
 
-Prefer these semantic MCP tools when the server is configured:
+Use these semantic MCP tools when the corresponding operation is required:
 
 - `collect_commit_context`
 - `collect_pr_context`
@@ -54,8 +44,14 @@ Prefer these semantic MCP tools when the server is configured:
 - `potential_to_issue`
 - `new_active_feature_folder`
 - `resolve_execute_hard_lock_prompt`
+- `resolve_atomic_plan_prompt`
+- `validate_orchestration_artifacts`
+- `run_poshqc_format`
+- `run_poshqc_analyze`
+- `run_poshqc_analyze_autofix`
+- `run_poshqc_test`
 
-Legacy VS Code command IDs remain historical source material only:
+Legacy VS Code command IDs are historical source material only and must not be invoked:
 
 - `drmCopilotExtension.collectCommitContext`
 - `drmCopilotExtension.collectPrContext`
@@ -69,74 +65,102 @@ Legacy VS Code command IDs remain historical source material only:
 
 ## Adapter Preconditions
 
-Before treating the MCP path as available, assume these prerequisites:
+Before starting any workflow that depends on this skill, the orchestrator must assume these prerequisites are mandatory:
 
-- the Codex client is configured with MCP server name `drmCopilotExtension`
-- the published extension or bridge is installed and built
-- an open workspace folder exists for workspace-targeted operations
-- `python` is on `PATH`
-- `pwsh` is preferred, with Windows PowerShell fallback when applicable
+- the Codex project is trusted so project `.codex/config.toml` loads,
+- the Codex client is configured with MCP server name `drm-copilot`,
+- the `drm-copilot` MCP server is active,
+- the required MCP tool is exposed by the active server,
+- an open workspace folder exists for workspace-targeted operations.
+
+If any prerequisite is missing, stop before mutating workflow state.
 
 ## Execution Order
 
 For any host-specific workflow step:
 
-1. Prefer the published `drmCopilotExtension` MCP tool when it covers the requested operation.
-2. If the MCP server is unavailable, determine whether a deterministic git or filesystem fallback is sufficient.
-3. If a deterministic fallback is sufficient, use it and record that the result is a fallback artifact rather than a canonical tool-produced artifact.
-4. If no MCP path or safe fallback exists, stop and report the missing automation dependency instead of inventing behavior.
+1. Identify the required `drm-copilot` MCP tool.
+2. Call that MCP tool.
+3. Validate the MCP response according to the calling workflow's contract.
+4. If the tool is unavailable, the call fails, or the response does not satisfy the contract, stop and record blocked state. Do not execute a replacement path.
 
 ## Current Adapter Guidance
 
 ### PR context collection
 
-- Preferred: call tool `collect_pr_context` on MCP server `drmCopilotExtension`.
+- Required tool: `collect_pr_context`.
 - When the caller already resolved a base branch, pass that base explicitly.
-- Current fallback: use deterministic git commands to reconstruct equivalent context when review workflows only need base/head, merge-base, commits, and changed files.
-- When using fallback, record the provenance in the generated review artifact.
 - For orchestrator remediation loops, PR-context refresh is mandatory after each remediation commit and before each re-review.
-- When the caller explicitly requires MCP tooling for PR-context refresh, do not silently downgrade to fallback; stop and report the dependency gap instead.
+- If the tool is unavailable or fails, stop. Do not reconstruct PR context from local git commands.
 
 ### Commit context collection
 
-- Preferred: call tool `collect_commit_context` on MCP server `drmCopilotExtension`.
-- If the MCP server is unavailable and the workflow only needs staged-diff summary, use non-destructive git inspection as fallback and record that provenance.
+- Required tool: `collect_commit_context`.
 - For orchestrator remediation loops, collect commit context only after `git add -A` and only when staged changes exist.
-- For orchestrator remediation loops, do not continue to commit-message generation without an on-disk commit-context artifact path produced by the selected adapter path.
-- When the caller explicitly requires MCP tooling for commit-context collection, do not silently downgrade to fallback; stop and report the dependency gap instead.
+- Do not continue to commit-message generation without an on-disk commit-context artifact path produced by the MCP tool.
+- If the tool is unavailable or fails, stop. Do not replace it with staged-diff inspection.
 
 ### Feature promotion and active feature folder creation
 
-- Preferred MCP tools:
-  - `new_potential_entry`
-  - `new_potential_bug_entry`
-  - `potential_to_issue`
-  - `new_active_feature_folder`
-- Current rule: use the MCP tools as the canonical path.
-- Execute these lifecycle operations as one ordered chain:
-  - create potential entry
-  - promote with `potential_to_issue`
-  - capture numeric issue number from promotion output
-  - create or check out `${promotion-type}/${short-name}-${issue-num}`
-  - create active feature folder with `new_active_feature_folder`
-- `new_active_feature_folder` is not an allowed bootstrap substitute for missing promotion state.
-- If `${issue-num}` is missing, non-numeric, or placeholder text, stop instead of continuing.
-- If the MCP server is unavailable, surface a precise dependency gap unless the caller explicitly requests a best-effort local-only fallback.
-- Do not synthesize GitHub issue state, active-folder scaffolding, or placeholder lifecycle variables unless the user explicitly requests a best-effort local-only fallback.
-- When a local-only fallback is explicitly approved, preserve the same ordered lifecycle and verification gates; do not skip directly to folder creation.
+Required tools:
+
+- `new_potential_entry`
+- `new_potential_bug_entry`
+- `potential_to_issue`
+- `new_active_feature_folder`
+
+Execute these lifecycle operations as one ordered chain:
+
+1. Verify route metadata and selected `${work-mode}` are persisted in the
+   canonical checkpoint.
+2. Create or verify pre-issue branch `${promotion-type}/${short-name}` before
+   `new_potential_entry` or `new_potential_bug_entry`.
+3. Create the potential entry with `new_potential_entry` or
+   `new_potential_bug_entry`.
+4. Promote with `potential_to_issue`.
+5. Capture numeric issue number from promotion output.
+6. Rename the branch to `${promotion-type}/${short-name}-${issue-num}`.
+7. Create the active feature folder with `new_active_feature_folder`.
+
+`new_active_feature_folder` is not an allowed bootstrap substitute for missing promotion state. If `${issue-num}` is missing, non-numeric, or placeholder text, stop before final branch rename or active folder creation. Do not synthesize GitHub issue state, active-folder scaffolding, or placeholder lifecycle variables.
 
 ### Customization publishing and hard-lock resolution
 
-- Preferred MCP tools:
-  - `push_down_copilot_customizations`
-  - `push_down_codex_and_agents_customizations`
-  - `resolve_execute_hard_lock_prompt`
-- If the MCP server is unavailable, stop unless the caller explicitly provides an approved alternate path.
+Required tools:
+
+- `push_down_copilot_customizations`
+- `push_down_codex_and_agents_customizations`
+- `resolve_execute_hard_lock_prompt`
+- `resolve_atomic_plan_prompt`
+
+If the required tool is unavailable or fails, stop.
+
+### Orchestration artifact validation
+
+Required tool:
+
+- `validate_orchestration_artifacts`
+
+Use this tool for canonical validation of plans, policy audits, code reviews, feature audits, and orchestrator state. For orchestrator completion, call it with `artifact_type: "orchestrator-state"` and `require_complete: true`.
+
+If the tool is unavailable or fails, stop. Do not substitute direct CLI validation for canonical orchestrator completion.
+
+### PowerShell quality gates
+
+Required tools:
+
+- `run_poshqc_format`
+- `run_poshqc_analyze`
+- `run_poshqc_analyze_autofix`
+- `run_poshqc_test`
+
+When a workflow requires PoshQC execution through MCP, use only these tools. If the required tool is unavailable or fails, stop.
 
 ## Output Requirements
 
-When this skill is used, the calling workflow should report:
-- which operation required host adaptation,
-- which direct adapter or fallback path was selected,
-- whether the result is canonical or fallback-only,
-- what dependency is missing when the step is blocked.
+When this skill is used, the calling workflow must report:
+
+- which MCP operation was required,
+- which `drm-copilot` tool was called,
+- whether the MCP response satisfied the calling contract,
+- the blocked-state reason when the MCP dependency is unavailable or fails.

package/resources/codex-and-agents-customizations/.agents/skills/repo-automation-adapter/agents/openai.yaml

@@ -1,5 +1,5 @@
 dependencies:
   tools:
     - type: "mcp"
-      value: "drmCopilotExtension"
+      value: "drm-copilot"
       description: "Published drm-copilot stdio MCP bridge for repository automation"

package/resources/codex-and-agents-customizations/.agents/skills/research-issue/SKILL.md

@@ -1,16 +1,6 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: research-issue
 description: Investigate the best implementation approach for a feature or bug by analyzing the codebase and external references, then writing structured findings to artifacts/research/.
-allowed-tools:
-  - Read
-  - Grep
-  - Glob
-  - WebFetch
 ---
 
 # Research Issue Skill

package/resources/codex-and-agents-customizations/.agents/skills/review-epic/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: review-epic
 description: Invoke the epic-review worker to produce epic-audit artifacts for an epic folder.

package/resources/codex-and-agents-customizations/.agents/skills/review-feature/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: review-feature
 description: Invoke the feature-review worker to produce feature-audit artifacts for an active feature folder.

package/resources/codex-and-agents-customizations/.agents/skills/review-staged/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
 name: review-staged
 description: Invoke the staged-review worker to produce staged-review artifacts from the staged diff.

package/resources/codex-and-agents-customizations/.agents/skills/self-explanatory-code-commenting/SKILL.md

@@ -1,12 +1,8 @@
-# Converted skill
-
-Applied rewrites:
-- None
-
 ---
+name: self-explanatory-code-commenting
 paths:
   - "**/*.py"
-description: Intent-first docstring and commenting standards. Applies to Python files.
+description: Intent-first docstring and commenting standards.
 ---
 
 # Code Commenting and Docstring Policy

package/resources/codex-and-agents-customizations/.agents/skills/skill-canonical-location-audit/SKILL.md

@@ -1,8 +1,3 @@
-# Converted skill
-
-Applied rewrites:
-- Rewrite Claude skill-directory references to the native skill root.
-
 ---
 name: skill-canonical-location-audit
 description: 'Audit skills for canonical-location duplication. Use when ensuring a canonical location for a given item is defined in exactly one skill and duplicates are flagged.'