From d8dc0bd1902ec4b4a5ece7adbac62550db531ba0 Mon Sep 17 00:00:00 2001 From: fausto Date: Thu, 23 Apr 2026 18:05:33 +0200 Subject: [PATCH] Update pipeline analysis workflow in SKILL.md to clarify artifact usage - Replace generic `` placeholder with `` to match actual command syntax - Add `` placeholder consistently across all pipeline commands - Clarify GitLab artifact workflow: only use artifacts when logs indicate output redirection - Split artifact commands into separate list and grep steps with clearer descriptions - Add blank line after artifact section for better readability --- skills/smith/SKILL.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/skills/smith/SKILL.md b/skills/smith/SKILL.md index 2b54ac6..564240a 100644 --- a/skills/smith/SKILL.md +++ b/skills/smith/SKILL.md @@ -68,9 +68,12 @@ Use `--help` on any command for flags. 6. **Report** only what the retrieved evidence supports and cite `URL`. ### Pipeline Analysis -1. Use `smith pipelines list --status failed` to focus on failed jobs. -2. Once you know the pipeline log ID, use `smith pipelines grep --reverse` to analyze the logs. -3. For GitLab artifact-backed failures, use `smith pipelines artifacts list ` and then `... artifacts grep ... ""`. +1. Use `smith pipelines list --status failed` to focus on failed jobs. +2. Once you know the pipeline log ID, use `smith pipelines grep --reverse` to analyze the logs. +3. **For GitLab** if pipeline logs indicate that output was redirected to a file then: + - Use `smith pipelines artifacts list ` to enumerate archive paths. + - Use `smith pipelines artifacts grep ""` to search within the artifacts. + ## Stop Conditions Stop narrowing and answer when any of these is true: