Sync OpenSpec skills to 1.5.0#2
Open
Raidriar7170 wants to merge 1 commit into
Open
Conversation
Raidriar7170
marked this pull request as ready for review
July 13, 2026 05:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
openspec-sync-specsskillWhy
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 --versionreports1.5.0. All five repo-local files are byte-identical to the installed official global OpenSpec 1.5.0 skills:244c1997aa8dd353578064b711c871d8ae692ae917de6de0782ee949ca3f24135d214ad332e83a1846cb06b8ac60ba70d68abace8ece333c41c653666f3635a9b88f88bc118c8e9be6dbbda49d9a905dcd57c6b66fc7e79d09b9cdc8bde52ecae188bea211e93de7051f1de9e5853ccdd3bd403b64b17b26961c7e77e4e2bd3e0f8d143167bb7738fb8e14aaac3a7c4a0490f607f571c224fc38c407b4db94a6Remote pre-merge audit
statusCheckRollup=[]; check-runstotal_count=0; commit statusestotal_count=0mainis not branch-protected; repository rulesets and applicable branch rules are emptyMERGEABLEandCLEANNo 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 --version—1.5.0OPENSPEC_TELEMETRY=0 openspec doctor --json—healthy=trueOPENSPEC_TELEMETRY=0 openspec validate --all --strict— 15/15 passedPYTHONPATH=src pytest -q tests/test_project_surface.py— 2 passedPYTHONPATH=src ruff check src tests— passedPYTHONPATH=src python scripts/check_current_truth_surface.py— passedgit diff --check origin/main...HEAD— passedMypy applicability
Status: N/A.
This PR changes no Python source, tests, typing configuration, or project configuration. Base and head have identical
srcandteststree object IDs, andgit diff --quiet origin/main...HEAD -- src tests pyproject.tomlpasses. 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
openspec-sync-specsand archive templates still contain some relativeopenspec/specs/<capability>/spec.mdwording. 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.AskUserQuestion,TodoWrite, andTask tool; Codex maps these semantically to its available interaction, planning, and subagent tools.