القائمة
Use this skill when looking at nightly test results or investigating test failures.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | skyline-nightlytests |
| description | Use this skill when looking at nightly test results or investigating test failures. |
Full documentation: ai/docs/mcp/nightly-tests.md
| Tool | Purpose |
|---|---|
get_daily_test_summary(report_date) | Daily report for all 6 folders → ai/.tmp/ |
save_test_failure_history(test_name, start_date, container_path) | Stack trace pattern analysis → ai/.tmp/ |
save_run_log(run_id) | Full test log for grep/search → ai/.tmp/ |
get_run_failures(run_id) | Stack traces for a specific run |
get_run_leaks(run_id) | Leak details for a specific run |
| Folder | Duration | Branch |
|---|---|---|
| Nightly x64 | 540 min | master (default) |
| Performance Tests | 720 min | master |
| Release Branch | 540 min | release |
| Release Branch Performance Tests | 720 min | release |
| Integration | 540 min | assigned |
| Integration with Perf Tests | 720 min | assigned |
get_daily_test_summary("2025-12-15") → read reportsave_test_failure_history to check if same root causesave_run_log when stack traces aren't sufficientFor server-side queries, examples, and detailed workflows, see ai/docs/mcp/nightly-tests.md.
ALWAYS load when working in pwiz_tools/Osprey (C# port), on maccoss/osprey (Rust), or debugging Osprey-Rust parity issues.
ALWAYS load before git commit, push, or PR - team-specific commit format differs from standard conventions.
ALWAYS load when working on LabKey Server modules (MacCossLabModules, targetedms), in a LabKey enlistment directory, or on GitHub issues/PRs in LabKey repositories.
ALWAYS load when working in pwiz_tools/Skyline, on GitHub issues labeled 'skyline', or TODOs referencing Skyline code.
Invoke when starting an autonomous overnight session ("this is a nighttime autonomous session"). Sets a deep-investigation posture - premium on progress and high-definition findings, expects 5-8 hours of work without check-ins.
ALWAYS load when investigating bugs, failures, or unexpected behavior - ensures root cause analysis before attempting fixes.