[EdbertChan]

Summary

Slow CI jobs are hard to speed up when nobody knows where the time goes. This adds a report listing each job step and its time.

The report reads step timings that Datadog already stores. It prints a table and a link to the same query.

It also adds the skill to the shared skill list, because the repo's check needs both together.

Review Claim

Approve a read-only report that shows how long each step of a CI job takes, using Datadog data.

Review Lane

behavior

Review Unit

product-skill

Safety Invariant

It only reads Datadog and GitLab. The token comes from the environment and is never printed or saved.

Slice Rationale

This is the first of two slices. The skill's list entry ships with it. The repo's registry check fails for a skill missing from the list, so the two cannot be separated:

without the entry (CI log, merge queue run): FAIL skill directory not in skills.toml: product/skills/ci-job-timing
with the entry (this pull request):          ok 60 skills in skills.toml match disk

Non-goals

• No change to how CI jobs run.
• No writes to Datadog or GitLab.
• No second report; that comes in the next slice.

Measured

none: this adds a new report and nothing existing to compare against

Test Plan

Test Plan

• python3 -m unittest product/skills/ci-job-timing/tests/test_ci_job_timing.py printed Ran 8 tests ... OK
• python3 engine/skills/make-pr/scripts/preflight.py --base origin/main --dry-run printed unit product-skill: 3 file(s), neutral 1 file(s): skills.toml and ok preflight passed
• python3 scripts/ci/check_skills_registry.py, check_skills_three_harnesses.py, check_ecosystem_boundaries.py, check_skill_file_refs.py, check_skill_test_coverage.py --base origin/main --head HEAD, check_skill_test_debt_no_growth.py, check_skill_trigger_mechanism.py, check_no_dated_provenance.py --base origin/main, check_no_new_comments.py --base origin/main, check_hook_test_coverage.py, check_no_silent_hook_except.py, check_rules_are_wired.py and check_no_tracked_local_artifacts.py each exited 0 on both commits
• Not run: the full run every tests/ dir step. Blocker: it takes about 54 minutes and runs in CI on this pull request
• Not run: a live query against Datadog. Blocker: it needs live Datadog access, which was not used for this slice
• Fixture vs live: the tests above use fixtures only; no live side effect was exercised

Revert Plan

Revert Plan

• Safe to revert? Yes
• Revert command: git revert <sha>
• Post-revert steps: None
• Data migration? No

🤖 Generated with Claude Code

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 1977db8e-0817-422b-adea-e91dc1adaa08)

[mergify]

Queued — the merge queue status continues in this comment ↓.

[EdbertChan]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-12 20:03 UTC · Rule: admin-bypass · triggered by @EdbertChan with the @mergifyio queue command
• ❌ Checks failed — 2026-10-12 20:24 UTC · on draft merge queue: checking #1332 + #1354 + #1358 + #1359 together on main (2f93d6c) #1361
• ✂️ Bisecting to identify the failing PR (round 1/1)
• ❌ Checks failed · on draft merge queue: checking #1354 on main (2f93d6c), stacked on #1332 #1364 · identified as the failing PR
• 🚫 Left the queue — 2026-10-12 22:06 UTC · at 0425a9ade08a9efc0d11033245dad1b1ef69230b

This pull request spent 2 hours 2 minutes 47 seconds in the queue, including 1 hour 35 minutes 50 seconds running CI.

Reason

The merge conditions cannot be satisfied due to failing checks

• test

Failing checks:

• ❌ test (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Waiting for

• check-success = test

All conditions

• check-success = test
• check-success = lint
• check-success = validate

Requeued — the merge queue status continues in this comment ↓.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: e67f17cc-93fa-4aa7-ac21-c0790f0fa04a)

[EdbertChan]

Revision history

#	Type	Changes	Reason	Date
1	initial	e93ea17		2026-10-13 04:06 UTC
2	unknown	e93ea17 → 44d8782		2026-10-13 04:06 UTC

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: bdde7ff2-73ee-4a84-baf0-99d317e0d28c)

[EdbertChan]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-13 04:08 UTC · Rule: admin-bypass · triggered by @EdbertChan with the @mergifyio queue command
• ❌ Checks timed out — 2026-10-13 04:08 UTC · on draft merge queue: checking #1354 + #1374 + #1360 together on main (d89f0c8) #1376
• ✂️ Bisecting to identify the failing PR (round 1/1)
• ✅ Checks passed · on draft merge queue: checking #1354 on main (d89f0c8) #1389
• ✅ Merged — 2026-10-13 05:51 UTC · at e4d3d1b582afb1e6e8657053daee252e1cd75975 · squash

This pull request spent 1 hour 43 minutes 44 seconds in the queue, including 1 hour 42 minutes 48 seconds running CI.

Required conditions to merge

• check-success = lint
• check-success = test
• check-success = validate

[EdbertChan]

Mergify repair stopped: PR #1354 is ready to land, but upper stack PR(s) #1356 are open without admin-bypass; a human must decide whether to include them in the admin-bypass landing stack or land them separately.