YAshhh29 opened a new pull request, #70477:
URL: https://github.com/apache/airflow/pull/70477

   The `aip-user-stories` skill is shared across agent runtimes, but its 
generated output currently targets a Claude-specific directory. Its 
verification workflow also assumes implementation code lives under 
`airflow-core`, which can miss features implemented in distributions such as 
`airflow-ctl`.
   
   This change makes generated playbooks portable and strengthens the existing 
verification promise by:
   
   - writing playbooks to Airflow's vendor-neutral `files/` output directory
   - distinguishing pasted AIP content from local file arguments
   - discovering implementation and package metadata across workspace 
distributions
   - requiring evidence for Verified, Adapted, and Unverified code examples
   - avoiding unsupported release-version claims
   - validating evidence, imports, prerequisites, and implementation status 
before writing
   
   The bundled playbook template now records release availability, required 
packages, runtime prerequisites, verification tier, and repository evidence.
   
   Validation:
   
   - `prek run check-merge-conflict --files ...`
   - `prek run end-of-file-fixer --files ...`
   - `prek run trailing-whitespace --files ...`
   - `prek run lint-markdown --files ...`
   - focused assertions for the skill's input, package discovery, evidence, 
validation, and output contracts
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — GitHub Copilot
   
   Generated-by: GitHub Copilot following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   ---
   Drafted-by: GitHub Copilot (no human review before posting)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to