ci-triage
Skill829 starsChanged 3 years agoMITView on GitHub
Diagnose failed, stuck, or missing Artemis CI checks and distinguish test defects from infrastructure failures.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- TanKaizokuO/claude-skillstheir own version, first seen Nov 8, 2026
- wannanbigpig/ai-engineering-collaborationtheir own version, first seen Nov 6, 2026
- me-cedric/agent-compasstheir own version, first seen Nov 1, 2026
- juzorei/ci-autopsytheir own version, first seen Nov 1, 2026
- andymai/brepjstheir own version, first seen Oct 9, 2026
- hyperledger-cacti/cactitheir own version, first seen Oct 9, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- NewFuture/DDNS★ 4.7ksame name
- nubjs/nub★ 4.4ksame name
- Mentra-Community/MentraOS★ 2.4ksame name
- levy-street/world-of-claudecraft★ 2.3ksame name
- hyperledger-cacti/cacti★ 412same name
- andymai/brepjs★ 142same name
- hyperledger-labs/splice★ 122same name
- fair-acc/gnuradio4★ 117same name
- 5throck/ai-workspace-standards★ 25same name
- syndicalt/zaxy★ 17same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- client-conventionsSkill
- e2e-pr-checkSkill
- liquibase-migrationSkill
- local-setupSkill
- server-arch-gatesSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use drafts only while the implementation is unfinished.
- Distinctive: line 17
Keep unverified checklist items open and require passing checks and approvals before merge.
- Very specific: line 33
All required CI Passed: check. A green draft run therefore does not validate its untested head for merge.
- Very specific: line 78
Use reference/known-failure-patterns.md to distinguish timeouts, architecture gates, missing workflow runs, and known harness failures from …
- Distinctive: line 93
Check the triggering event and checked-out revision when identifying the workflow version.
- Distinctive: line 110
Leave that option false to analyze the selected branch itself.
- Very specific: line 130
Read the published report at https://api.securityscorecards.dev/projects/github.com/ls1intum/Artemis and check its date and commit before …
- Very specific: line 144
Use skills/server-arch-gates/SKILL.md for architecture and style checks, skills/write-tests/SKILL.md for JUnit and Vitest, and …
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Triage a red Artemis build
Keep completed implementations available for CI and review
Use drafts only while the implementation is unfinished. Once implementation is complete, open the PR
as non-draft or mark it ready for review immediately. Draft pull_request runs defer the entire
ci-test.yml workflow (server, client and AI worker sandbox tests), E2E, CodeQL and review bots.
Relevant style, lint, architecture and type checks still run on public runners. Test TypeScript
compilation runs in Quality / Client Compilation for drafts; the WAR and draft test-server image builds
remain available. Integration-test feedback arrives after ready-for-review or a manual full run.
Pending or failing CI, reviews and test-server validation do not by themselves require draft status.
Keep unverified checklist items open and require passing checks and approvals before merge; follow
PR readiness.
Identify the failing check
gh pr checks <pr-number>
gh run view <run-id> --log-failedThe aggregate All required CI Passed is defined in .github/workflows/ci.yml.
Trace the failing check through its called workflow; job names are prefixed by the caller
(for example, Quality / Server Code Style). Check the repository's required-check settings
before claiming that an advisory failure blocks merging.
Draft runs report Draft checks passed (tests deferred) instead of the required
All required CI Passed check. A green draft run therefore does not validate its untested head
for merge. The ready_for_review event starts a normal run, including when the head SHA is unchanged;
wait for its required checks before marking the PR ready to merge.
PR and non-PR E2E jobs can use different topologies: a pull request runs one node, develop runs three
nodes with Redis (Valkey) as distributed data provider. Compare their definitions in
.github/workflows/ci-e2e.yml before treating a develop-only failure as flaky.
Check the validation scope
Ready pull requests run explicit affected server class plans and related client specs. The server planner's summary lists its class count and modules; mandatory architecture and source-scanning guards remain included, as does the Gocast handler guard. The client job prints every selected spec, including filesystem-reading guardrails whose source reads have no import edges. Every changed client graph seed must have related tests; guardrails cannot hide an untested seed. Shared leaf utilities use the import graph. Shared contracts, configuration, missing history and ambiguous dependencies fall back to the full suite. Check the actual planner/helper output rather than assuming a PR always ran a subset.
The two Stylelint entry points, config/stylelint/stylelint.config.json and
config/stylelint/stylelint.config.js, are client-only inputs. A PR confined to those files skips
server tests; when mixed with Java changes, they do not expand the affected server class plan.
Other configuration and server disk-input changes retain the conservative fallback.
Affected runs keep test results but omit whole-project coverage gates and artifacts. The PR coverage section states the scope and result; a selected green run does not prove full-suite coverage. E2E selects mapped modules plus declared cross-module consumers, changed specs, and login/logout/health smoke tests. Its dependency contract must account for all discovered specs. Ordinary eligible PRs intentionally skip Phase 2; full callers retain the disjoint complement. Documentation and unit tests accompanying source changes do not force full E2E. Shared runtime, configuration, helpers and unknown inputs require the full suite; missing expected results still fail.
Pushes to develop/main/release branches, merge-group events, releases and manual CI runs use full suites when the Test stage is selected. To validate the complete PR branch before merging, dispatch CI with that branch and Bypass change detection and run every job enabled. Without that override, area filtering can skip an irrelevant Test stage, including on a draft branch. Re-running a ready PR event preserves its affected scope; re-running a draft PR event keeps tests deferred. A merge group only provides pre-merge full validation when the repository uses it.
The current-revision check runs immediately as a step inside Detect Changed Areas, using
.github/scripts/pr-ready.js and the job's existing checkout. It adds no separate runner or
checkout. API failures fail the required gate closed. Obsolete revisions skip expensive work
and are superseded by the new PR run.
Classify before changing code
Use reference/known-failure-patterns.md to distinguish timeouts, architecture gates,
missing workflow runs, and known harness failures from application defects. A single failure
is not evidence of flakiness; compare logs and execution conditions.
A latest PR run that is pending with no jobs can be waiting for an obsolete run to release its concurrency slot. Follow the cancellation entry in the reference before rerunning or cancelling jobs.
Re-run when justified
- Server Tests: never use
gh run rerun --failed. The suite's sharding and reporting mean a partial re-run does not reproduce the original conditions. Use a full re-run:gh run rerun <run-id>. - No run started at all: this is not something a re-run fixes. See the "no CI at all" and "dropped event" entries in the reference file.
- A workflow file changed in the branch: classic PATs need the
workflowscope to push it. Check the triggering event and checked-out revision when identifying the workflow version.
Sonar badges stay unchanged after a merge
Compare api/project_analyses/search?project=ls1intum_Artemis with the merged SHA, then inspect the
actual Build and analyze step. A scan that exits before publication leaves the previous analysis
and badges unchanged. Scanner 6+ has a separate JVM; SONAR_SCANNER_JAVA_OPTS sizes its heap,
while org.gradle.jvmargs sizes Gradle. The workflow assigns the scanner 6 GiB.
Sonar is required on relevant ready PRs and is included in All required CI Passed. Scanner, upload and server-side quality-gate failures block merging. Both PR and branch scans wait for the server verdict. To test a repaired workflow and refresh the actual default branch before merging it:
gh workflow run ci-sonar.yml --ref <workflow-fix-branch> -f analyze_default_branch=trueLeave that option false to analyze the selected branch itself. Check the job summary's analyzed branch/SHA and the completed Sonar analysis revision. Coverage lookup requires that exact SHA, both complete artifacts and successful full test jobs; unrelated CI failures do not invalidate it. The required scanner waits for the server verdict; still confirm the published source revision when diagnosing badges or a manually dispatched recovery. See workflow policy.
Affected tests emit separate Sonar Client Coverage (selected-spec LCOV) and Sonar Server Coverage (selected execution data). Sonar generates Java XML on a GitHub-hosted runner. These partial reports never feed full-project badges or Codacy; no test suite is rerun for analysis. Missing or failed producer data cannot be imported as successful coverage.
Fork and token-restricted PRs (including Dependabot) use a secretless exact-head/source-branch/target/public-gate verifier. A maintainer must
review the exact commit, promote it to internal chore/sonar/pr-<number>, dispatch the trusted default
branch's Sonar workflow with pull_request_number=<number>, then rerun only the original Sonar
verification job. Never automatically execute fork build scripts with the token. See the workflow
policy for the promotion procedure. Head or target changes invalidate evidence. Metadata-only
edits neither replace canonical validation nor cancel active coverage reporting.
Investigate Scorecard findings
Read the published report at
https://api.securityscorecards.dev/projects/github.com/ls1intum/Artemis and check its
date and commit before comparing it with the working tree. Branch-protection findings
cover release branches as well as develop; missing release signatures refer to release
assets, not just GitHub's attestation store.
Pin every external action, including actions/* and github/*, to a full commit SHA
with a # vX.Y.Z comment. Resolve the upstream tag to its commit rather than guessing
the hash. Renovate's helpers:pinGitHubActionDigests preset maintains these references.
See .github/workflows/README.md for the workflow policy. Run actionlint -shellcheck=
after editing workflows.
Reproduce a defect
Use skills/server-arch-gates/SKILL.md for architecture and style checks,
skills/write-tests/SKILL.md for JUnit and Vitest, and skills/e2e-pr-check/SKILL.md
for Playwright. Do not mask an unexplained failure with retries or a larger timeout.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

