Skip to content

Sync OpenSpec skills to 1.5.0#2

Open
Raidriar7170 wants to merge 1 commit into
mainfrom
codex/sync-openspec-skills-1.5.0
Open

Sync OpenSpec skills to 1.5.0#2
Raidriar7170 wants to merge 1 commit into
mainfrom
codex/sync-openspec-skills-1.5.0

Conversation

@Raidriar7170

@Raidriar7170 Raidriar7170 commented Jul 13, 2026

Copy link
Copy Markdown
Owner

Summary

  • sync four repo-local OpenSpec Codex skills from generatedBy 1.3.1 to 1.5.0
  • add the official openspec-sync-specs skill
  • adopt store-aware planning paths and resolved OpenSpec action context

Why

The installed OpenSpec CLI and official global Codex skills are now 1.5.0, while this repository still carried the older 1.3.1 generated skill instructions and lacked the sync-specs workflow.

Scope

This PR changes only five files under .codex/skills/. It does not modify application code, OpenSpec specifications, datasets, reports, training, prediction, UI, or execution state.

Official-source parity

openspec --version reports 1.5.0. All five repo-local files are byte-identical to the installed official global OpenSpec 1.5.0 skills:

Skill SHA-256
openspec-apply-change 244c1997aa8dd353578064b711c871d8ae692ae917de6de0782ee949ca3f2413
openspec-archive-change 5d214ad332e83a1846cb06b8ac60ba70d68abace8ece333c41c653666f3635a9
openspec-explore b88f88bc118c8e9be6dbbda49d9a905dcd57c6b66fc7e79d09b9cdc8bde52eca
openspec-propose e188bea211e93de7051f1de9e5853ccdd3bd403b64b17b26961c7e77e4e2bd3e
openspec-sync-specs 0f8d143167bb7738fb8e14aaac3a7c4a0490f607f571c224fc38c407b4db94a6

Remote pre-merge audit

Check Status Evidence
GitHub Actions / check-runs N/A statusCheckRollup=[]; check-runs total_count=0; commit statuses total_count=0
Required checks N/A main is not branch-protected; repository rulesets and applicable branch rules are empty
Merge conflict PASS GitHub reports MERGEABLE and CLEAN
Conversation comments PASS 0
Review submissions PASS 0
Unresolved review threads PASS 0

No remote CI or required check is configured, so this PR does not claim a remote-CI pass. The local validation below is the available automated merge evidence.

Validation

  • openspec --version1.5.0
  • byte comparison against all five installed official global skills — 5/5 PASS
  • OPENSPEC_TELEMETRY=0 openspec doctor --jsonhealthy=true
  • OPENSPEC_TELEMETRY=0 openspec validate --all --strict — 15/15 passed
  • PYTHONPATH=src pytest -q tests/test_project_surface.py — 2 passed
  • PYTHONPATH=src ruff check src tests — passed
  • PYTHONPATH=src python scripts/check_current_truth_surface.py — passed
  • git diff --check origin/main...HEAD — passed
  • worktree — clean
  • independent read-only diff review — PASS; no Must Fix or Should Fix

Mypy applicability

Status: N/A.

This PR changes no Python source, tests, typing configuration, or project configuration. Base and head have identical src and tests tree object IDs, and git diff --quiet origin/main...HEAD -- src tests pyproject.toml passes. Running or restating the unrelated historical Mypy debt would not test this Markdown-only skill sync.

Browser viewport QA

Status: N/A.

All changed files are Markdown skill instructions under .codex/skills/. There are no HTML, CSS, JavaScript, TypeScript, UI component, or rendered application changes.

Deferred risks and boundaries

  • Remote CI and required checks are not configured; merge confidence relies on the local parity and validation packet above.
  • The official OpenSpec 1.5.0 openspec-sync-specs and archive templates still contain some relative openspec/specs/<capability>/spec.md wording. In a standalone store launched from another repository, that wording may be less precise than the new store-aware planning context. This is an upstream-template follow-up; changing it here would break official byte parity and reproducibility.
  • The official templates retain generic tool names such as AskUserQuestion, TodoWrite, and Task tool; Codex maps these semantically to its available interaction, planning, and subagent tools.
  • No claim is made about application behavior, model quality, training, prediction, A100 execution, datasets, or evaluation results.

@Raidriar7170
Raidriar7170 marked this pull request as ready for review July 13, 2026 05:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant