Skip to content

docs(vera): align Linear skill prompt body#86

Closed
cjarguello wants to merge 2 commits into
mainfrom
codex/align-linear-qa-skill-prompt
Closed

docs(vera): align Linear skill prompt body#86
cjarguello wants to merge 2 commits into
mainfrom
codex/align-linear-qa-skill-prompt

Conversation

@cjarguello
Copy link
Copy Markdown
Member

Summary

  • align the saved skill prompt body to the Linear agent version

Notes

  • title headers may differ; body now matches the Linear settings prompt

@cjarguello cjarguello requested a review from a team as a code owner April 1, 2026 02:28
@cjarguello
Copy link
Copy Markdown
Member Author

Closing. The repo should match the GitHub canonical prompt body; no additional changes required.

@cjarguello cjarguello closed this Apr 1, 2026
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1e72cf90b3

ℹ️ 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".


Rules:
- If critical context is missing, fail closed as `QA_RESULT=FAILED` with `qa-failed`
- If QA cannot safely reach pass/fail (legacy `NO_VERDICT`), emit `QA_RESULT=SKIPPED` with `qa-skipped` and explain what is missing
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restrict SKIPPED rule to explicit legacy NO_VERDICT cases

This new rule tells Vera to emit QA_RESULT=SKIPPED whenever it cannot safely decide pass/fail, which conflicts with the preceding fail-closed rule (QA_RESULT=FAILED when critical context is missing). In practice, incomplete handoffs now have two valid outcomes, so different runs can produce different gate results for the same missing-context scenario; this weakens the intended fail-closed behavior described in linear/docs/process/vera_qa_lane_contract_v1.md (hard rule section).

Useful? React with 👍 / 👎.

- Final line:
- `QA_VERDICT: PASSED`
- or `QA_VERDICT: FAILED`
- QA label: `qa-passed` or `qa-failed`
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Allow qa-skipped in the required report label schema

The prompt now permits QA_RESULT=SKIPPED and qa-skipped, but the required verification_report.md structure still says the QA label is only qa-passed or qa-failed. When a skip path is used, the agent is forced to violate either the report schema or the result-token rules, producing inconsistent artifacts and receipts that are harder to consume reliably.

Useful? React with 👍 / 👎.

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