←Leaderboard/Software Engineering/loopkit
Last commit on July 14, 2026·Created on June 30, 2026

Archive228/loopkit

“A collection of battle-tested skills and a minimal harness for coding agents”
Combined rank
#431
across all skills
In Software Engineering
#35
category rank
Stars
757
0.0% in last 7d
Forks
124
-1.6% in last 7d
Watchers
4
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

Loopkit provides a structured set of skills designed to standardize AI coding workflows. It helps developers using agents like Claude Code, Cursor, and Gemini CLI maintain higher output quality through specialized passes for accessibility auditing and session memory management.

The toolkit focuses on the gaps in AI-generated code, offering specific routines to catch UI accessibility failures and a machine-readable decision tracking system to preserve context across sessions.

WHO IT'S FOR
AI agent power users
standardize AI coding workflows with battle-tested skills
Frontend engineers
audit AI-generated UI for accessibility failures
Backend / infrastructure engineers
verify authorization and ownership on API endpoints
Technical leads / architects
implement adversarial verification for AI code changes
Repository contents

53 skill files

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

Setup

Install Loopkit in the current project with curl

Installs: Complete Loopkit project bundle: the .claude harness, repository skills installed under .claude/skills, and available root harness files. Existing files are skipped by default. · Claude Code, Cursor, Codex, Gemini CLI

Before you start
  • Bash
  • curl
  • tar
  • mktemp
  • find
  • An existing destination project directory

Run from: The project directory where Loopkit should be installed

  1. In a terminal, change to the destination project directory, then run the installer. It installs into the current directory and skips existing files by default.

    curl -fsSL https://raw.githubusercontent.com/Archive228/loopkit/main/install.sh | bash
install.sh ↗ · Checked Oct 2, 2026README.md ↗ · Checked Oct 2, 2026

Give it something to do.

Suggested first task

Check a completed diff against its goal

Uses adversarial-verify

  • Goal specification path, such as PROMPT.md
  • Diff, patch, or commit range to review
Use the adversarial-verify skill to review the goal specification at [GOAL_SPEC_PATH] against the diff identified by [DIFF_OR_COMMIT_RANGE]. Do not run or change the code and do not propose fixes. Check every changed line for the documented shortcuts and return only the skill's JSON result.
Suggested first task

Assess a schema change before migration

Uses schema-diff

  • Path or content for the old schema
  • Path or content for the new schema
Use the schema-diff skill to compare [OLD_SCHEMA_PATH] with [NEW_SCHEMA_PATH]. Return a risk-ranked list of changes, explain data-loss, reversibility, and backfill concerns for destructive changes, and give a go/no-go recommendation with the safe rollout order.
skills/schema-diff/SKILL.md ↗ · Checked Oct 2, 2026
Suggested first task

Find the three riskiest untested paths

Uses coverage-gaps

  • Code path or component to inspect
  • Relevant tests or coverage report
Use the coverage-gaps skill to inspect [CODE_SCOPE] together with [TEST_OR_COVERAGE_INPUT]. Identify the three highest-risk untested behavior paths, rank them by blast radius, and describe the test to add for each. Focus on error paths, boundaries, branches, and stateful ordering rather than the headline coverage percentage.
skills/coverage-gaps/SKILL.md ↗ · Checked Oct 2, 2026