Leaderboard/Code Quality/linus-torvalds-skills
Last commit on April 23, 2026·Created on April 22, 2026

leopiney/linus-torvalds-skills

Teaches an AI to hate bad abstractions and love simple data structures.
Combined rank
#636
across all skills
In Code Quality
#20
category rank
Stars
284
+0.3% in last 7d
Forks
10
0.0% in last 7d
Watchers
0
0 watchers 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

The Torvalds Doctrine is a set of aggressive coding guidelines that turns an AI assistant into a disciplined reviewer. It enforces data structure supremacy, rejects overengineering, demands proof over hand-waving, and calls out bogus shit on sight. Developers who want their AI-generated code to stay grounded in hardware reality and avoid enterprise sludge will find a blunt counterpart in the chat.

WHO IT'S FOR
Software Engineers Using AI Coding Assistants
enforce code quality in AI patches
Technical Leads and Code Reviewers
establish review criteria for AI-generated contributions
Open-Source Maintainers
guard against low-quality AI patches in projects
Platform and DevEx Teams
embed coding standards into AI tooling configurations
Repository contents

1 skill file

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

Follow the documented setup, then try a first task.

Install with npx skills

Installs: Complete leopiney/linus-torvalds-skills bundle

  1. Run this terminal command to add the documented repository bundle.

    npx skills add leopiney/linus-torvalds-skills
.claude-plugin/plugin.json · Checked Sep 18, 2026README.md · Checked Sep 18, 2026

Give it something to do.

Suggested first task

Review a small patch with the Torvalds Doctrine

Uses torvalds-doctrine

  • A patch or diff path replacing [PATCH_OR_DIFF_PATH]
  • Any relevant compatibility constraints or expected behavior
Use the torvalds-doctrine skill to review the patch at [PATCH_OR_DIFF_PATH]. Identify up to three concrete problems involving the data model, unnecessary complexity, unrelated changes, compatibility regressions, or unsupported correctness/performance claims. For each problem, cite the relevant changed lines, explain the technical impact, recommend the smallest corrective change, and name a test, benchmark, or reproducible check that would verify it. Review the patch only; do not modify files.