Pranaykarvi commented on issue #62500: URL: https://github.com/apache/airflow/issues/62500#issuecomment-4288292376
@jason810496 @potiuk — updated PoC since my last comment, addressing the questions raised on Mar 22. **Draft PR:** #64008 **Branch:** https://github.com/Pranaykarvi/airflow/tree/feat/agent-skills-poc ### What was added since the last update **Source of truth alignment** contributing-docs/*.rst is the primary source. Skill blocks are embedded inline in 03_contributors_quick_start.rst. AGENTS.md is secondary. The extractor scans both and fails CI if skills.json drifts. **Real E2E evidence (not hypothetical)** DX_REPORT.md was rewritten with actual terminal output — real error messages from running wrong commands on host, real output from the runtime API resolving to correct commands. No "may suggest" or "high risk" language. **context: either skill** Added run-tests-in-breeze with context: either — first skill that exercises the host/Breeze branching in the runtime API with real data. On host it returns the uv-first command, inside Breeze it returns bare pytest. **E2E scenario harness** scripts/ci/agent_skills/eval/scenario_01_fix_and_test.md — a step-by-step "exam" an agent or human can follow to verify the skills work end-to-end for a real contribution workflow (stage → static checks → targeted test). **Extractor bug fixed** Regex lookahead was swallowing trailing RST prose into expected_output for the last skill block in a file. Fixed and verified all 10 skills have clean expected_output. **All Copilot review comments addressed** SKILLS_JSON path resolution, drift key completeness, duplicate ID detection, subprocess timeouts, build_graph validation, README contradictory quote. ### Current state - 10 skills (9 host, 1 either) - 29/29 tests passing - ruff: clean - drift check: in sync - 3 prek hooks wired in CI ### Still open - scenario_02 (Breeze-context E2E) - no context: breeze skill yet - justfile / mise launcher (per gsemet's suggestion) -- 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]
