SKILLEMALL.ai
GitHub ↗ RU Sign in

CC git-history-recon

Analyze git repository history to produce a codebase risk profile before code review. Probes repo size, runs 7 parallel git analysis pipelines (hotspots, bug magnets, bus factor, contributor momentum, firefighting frequency, newly added files), cross-references hotspots with bug magnets to identify high-risk files with primary owner annotation, and writes walkthrough/recon-report.md. Use before code review to prioritize reviewer attention, at the start of linear-walkthrough Phase 1 Discovery to weight file coverage, or when onboarding to an unfamiliar codebase.

Jamie-BitFlight/claude_skills Claude Code author: Jamie-BitFlight MIT 1 file body ≈ 7 233 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Analyze git repository history to produce a codebase risk profile before code review.

As a process C 60/100 · Has gaps — References files that are not bundled: ../../../rules/large-file-write-strategy.md, ../../../rules/silent-failure-prevention.md, ../linear-walkthrough/SKILL.md

AnalyzerSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
C
60/100
Has gaps
References files that are not bundled: ../../../rules/large-file-write-strategy.md, ../../../rules/silent-failure-prevention.md, ../linear-walkthrough/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 7233 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../../rules/large-file-write-strategy.md
  • warning missing-ref reference to a missing file: ../../../rules/silent-failure-prevention.md
  • warning missing-ref reference to a missing file: ../linear-walkthrough/SKILL.md
  • warning missing-ref reference to a missing file: ../create-merge-request-changelog/SKILL.md
  • warning missing-ref reference to a missing file: assets/exclude-patterns

Process rating: all ten parameters 60/100

Will not run. References files that are not bundled: ../../../rules/large-file-write-strategy.md, ../../../rules/silent-failure-prevention.md, ../linear-walkthrough/SKILL.md
  • 0Tools and files. 5 referenced file(s) missing: ../../../rules/large-file-write-strategy.md, ../../../rules/silent-failure-prevention.md, ../linear-walkthrough/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 30 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 70Execution cost. Instruction body is 7233 tokens
  • 100Steps. 20 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 567: enough signal without eating the budget
  • +4Structure: 39 headings
  • +3Step-by-step instructions: 20 items
  • +3Output format is stated explicitly
  • +4Has examples (24 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.