Menu
Inspect local OpenSymphony workspace artifacts without changing repo-owned policy files.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | inspect-opensymphony-artifacts |
| description | Inspect local OpenSymphony workspace artifacts without changing repo-owned policy files. |
Use this skill when you need to confirm what OpenSymphony generated for the current issue workspace.
WORKFLOW.md, AGENTS.md, and other checked-in repo files as repo-owned policy..opensymphony/ as additive local state and audit output..opensymphony/issue.json.opensymphony/run.json.opensymphony/conversation.json.opensymphony/generated/issue-context.md.opensymphony/generated/session-context.json.opensymphony/prompts/.opensymphony/runs/.opensymphony/ unless the task explicitly asks for fixture changes.Import OpenSymphony memory for work completed outside the orchestrator and Linear tracker. Use when asked to capture GitHub PRs, merge commits, direct commits, or other off-run-loop work into project memory by creating a temporary YAML evidence file, running `opensymphony memory import`, and syncing docs.
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
Pull the latest configured target branch into the current local branch and resolve merge conflicts (aka update-branch). Use when syncing a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
Use this skill when a docs/tasks/task-package.yaml planning wave should be validated, previewed, or published to Linear with milestone assignments, parent/sub-issue relationships, blocker relations, and publish state.
Use repo-local GraphQL helpers to read and write Linear through `LINEAR_API_KEY`.