Repository navigation
docs(skills): add Symphony ticket requirements - #14
Conversation
Define the project, Repository label, execution and dependency requirements for Linear tickets handed to Symphony. Include essential issue content and verification after registration without duplicating ordinary Linear usage. Keep Personal Symphony explicit for this environment while resolving IDs and other environments from their configuration. Validation: skill quick validation, procedure review, diff check, and standalone PR body validation passed. Full Elixir checks are not applicable for this skill-only change. Co-authored-by: Codex <codex@openai.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ebaa09b03e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Trigger the skill for creation and updates as well as requirement checks. Keep new work outside active states until its fields and dependencies are saved and verified, then activate and read back the final state. Apply optional routing requirements only when configured. Verify assignee IDs when a filter exists, resolving me against Symphony's identity rather than the ticket author's identity. Preserve already-running issue states. Validation: skill validator, diff check, standalone PR body lint, and procedure walkthroughs passed. Full Elixir validation is not applicable for this skill-only change. Co-authored-by: Codex <codex@openai.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c630780b46
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Stage new issues and queued updates in a non-active, non-terminal state before editing fields, and verify the saved issue before activation. Coordinate with execution for running or indeterminate issues instead of automatically resetting their state. Document that the standard Linear client checks blockers only in Todo. Use Todo when active, or retain blocked work outside active states until all blockers are terminal. Keep optional assignee requirements conditional. Validation: skill validator, diff check, standalone PR body validation, and walkthroughs for queued updates, running/unknown states, and blocker routing passed. Full Elixir validation does not apply to this skill-only change. Co-authored-by: Codex <codex@openai.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b78c19e6f9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Limit ticket creation and updates to inactive, non-terminal issues. Leave active and unknown-state issues unchanged and hand them to the execution-side operating procedure, even when they appear queued. A runtime snapshot cannot prevent a scheduler from claiming an issue before a later state change. Remove that check-then-reset procedure instead of adding scheduler pause or reservation machinery to this skill. Validation: skill validator, diff check, standalone PR body lint, and walkthroughs of inactive, active queued, running, and unknown-state issues passed. Full Elixir validation does not apply to this skill-only change. Co-authored-by: Codex <codex@openai.com>
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 71fa620f6c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Name Todo as this deployment's initial-work state and exclude approval or rework states from new execution. Other deployments use their configured initial-work state while preserving the dependency condition. Do not repeat a create with an unknown outcome. Hold execution until the existing issue is identified instead of adding a creation retry protocol. Validation: skill validator, diff check, standalone PR body validation, and walkthroughs for lifecycle states and ambiguous creates passed. Full Elixir validation does not apply to this skill-only change. Co-authored-by: Codex <codex@openai.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d2bba4d82d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Specify Backlog as this deployment's pre-execution holding state and use an equivalent initial holding state elsewhere. Exclude Human Review and other review or approval stages even when they are inactive. Hand existing issues outside the unstarted holding state to execution without mutation. Review-stage requirement changes follow rework instead of invalidating the requirements of a review-ready PR in place. Validation: skill validator, diff check, standalone PR body lint, and walkthroughs of Backlog, active, Human Review, terminal, and unknown issues passed. Full Elixir validation is not applicable to a skill-only change. Co-authored-by: Codex <codex@openai.com>
1 participant
Context
Linear tickets need the monitored project and a valid Repository child label before Symphony can process them. Ticket authors need reusable requirements that respect each deployment's optional routing conditions.
TL;DR
Add a concise skill for preparing and verifying Linear tickets before handing them to Symphony.
Summary
Alternatives
Test Plan