AC stack-rebase
Cascades a rebase through an entire PR stack after a base PR merges or upstream changes
Cascades a rebase through an entire PR stack after a base PR merges or upstream changes
As a process C 55/100 · Has gaps — weak spots: result and completion, consistency, running it twice
ProcedureGitHubSoftware developmentAI and agentsCommercetype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_plugin"
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 13 mutating operations with no state check
- 40Consistency. Frontmatter name (stack-rebase) differs from the folder (nm-sanctum-stack-rebase)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 20 steps
- 100Execution cost. Instruction body is 1379 tokens
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 87: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 16 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.
External checks
ClawHub: suspicious
This skill does what it says, but its very broad triggers could invoke a force-push and PR-edit workflow in situations where the user only asked about git or PRs generally.
LLM: suspicious (high) · VirusTotal: · 26 Aug 2026