auto-linter
Run linters/formatters on changed files and apply safe, mechanical fixes. Use in Flow 3 and Flow 4.
Browse published AI skills maintained by EffortlessMetrics. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
11Repository stars across indexed skills
0Repository forks
43Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Run linters/formatters on changed files and apply safe, mechanical fixes. Use in Flow 3 and Flow 4.
Run the relevant tests for the current change and summarize results. Use in Flow 3 (Build) and optionally in Flow 4 (Gate).
Publish gate secrets scanning. Use for: safe_to_publish, scan for secrets, redact in-place. Determines publish gate status. Scan files for secrets (locations only - NEVER prints secret content). GitHub tokens,...
Grep/wc replacement for .runs artifacts. Use for: count, extract, Machine Summary, receipt reading, marker counts. Null-safe counting (REQ/NFR/QID/RSK markers), YAML block parsing, BDD scenario counting. Determ...
Open questions register. Use for: QID generation, OQ-SIG-001 format IDs, append questions, open_questions.md. Generate sequential QIDs, append questions with context. Use in clarifier when registering open ques...
Update index.json status. Use for: upsert index.json, update status/last_flow/updated_at. Deterministic writes - stable diffs, no creation. Use only in run-prep and *-cleanup agents. Invoke via bash .claude/scr...
Run policy-as-code checks (e.g., OPA/Conftest) based on the policy_plan. Use in Flow 2 and Flow 4.
Diagnose and repair selftest failures by running diagnostic commands and proposing fixes
Run the relevant tests for the current change and summarize results. Use in Flow 3 (Build) and optionally in Flow 4 (Gate).
Run policy-as-code checks (e.g., OPA/Conftest) based on the policy_plan. Use in Flow 2 and Flow 4.
Run linters/formatters on changed files and apply safe, mechanical fixes. Use in Flow 3 and Flow 4.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.