DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to install the three Finn Loop skills into a GitHub repo with Finn Loop

Copy the finn-spec, finn-build, and finn-review skills into a repo and check that the prerequisites are working.

Credentials. The GitHub CLI must be authenticated with write access to the target repo, so the account used can push code changes there.

Who it is forA developer setting up Finn Loop for the first time in a GitHub repo with a Linear team who wants the skills available in Claude Code.

The problemThe skills need the right Claude Code version, a working gh login, Linear labels, and a team key before they can run.

The outcomeThe three skills appear in /skills, and a smoke test confirms Linear and GitHub reads succeed.

What you need first

  • A Git repository hosted on GitHub with a working origin remote
  • Claude Code 2.1.71 or newer
  • A Linear workspace and team with the Linear connector enabled in Claude Code
  • The GitHub CLI (gh) authenticated with write access to the target repo
  • At least one required GitHub status check if you want fully automated loop-approved verdicts

Steps

  1. Check the Claude Code version with claude --version and confirm it is 2.1.71 or newer.
  2. Check GitHub access with gh auth status and gh repo view.
  3. Paste the install prompt from the README into Claude Code inside the repo, and give it your Linear team key when asked.
  4. Run /reload-skills (or restart Claude Code), then run /skills and confirm finn-spec, finn-build, and finn-review are listed.

Prompt for your agent

Inside the GitHub repo at <repo path>, follow the Finn-loop install steps from the README of finn/Finn-loop using the Linear team key <team key>. Expected output: the three SKILL.md files under .claude/skills and a smoke-test report. Verify that /skills lists finn-spec, finn-build, and finn-review.

Caveat. The install prompt tells the agent to detect the repo's real default branch and confirm the authenticated account can push, so verify those results before trusting the setup.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page