Set up
Skills are installed by placing their folder where your agent loads skills.
The download comes from github.com/rene-poulsen/jean-claude itself, not from our server, so what you get is exactly what its author published.
Install instructions come from the README
README
synced Oct 22, 2026jean-claude
A collection of Claude Code skills, commands, agents and hooks.
Skills
| Skill | What it does |
|---|---|
| my-week | Lists every commit you made this week across your local git repos, grouped by repo, with the Claude Code tokens and cost behind each commit. |
| plan-my-week | Turns your WorkBook bookings into Outlook calendar events, placed around your existing meetings. Windows + classic Outlook. |
| 4k-website-recording | Smooth 4K 60 fps screen recordings of websites (scrolling, hovering, clicking through pages) for showreels, portfolios and case videos. |
| lighthouse-test | Lighthouse test on mobile and desktop, with a report that traces each problem to your code and suggests fixes. |
Each skill's README explains what you need, how to set it up and how to use it.
Commands
| Command | What it does |
|---|---|
| feature-pr | /feature-pr <what you fixed and why> moves your uncommitted changes to a new branch off development/develop/dev, commits with a generated branch name and message, pushes, opens a PR and shows it in your default browser. Needs the GitHub CLI for GitHub repos. |
| bug-pr | /bug-pr <the bug and what caused it> does the same for a bug fix: a bugfix/ branch, a commit that explains symptom, cause and fix, and a PR with steps to reproduce and how to verify. Needs the GitHub CLI for GitHub repos. |
| hotfix-pr | /hotfix-pr <the bug and what caused it> for urgent fixes to what's live: a hotfix/ branch off main/master, a PR into production and a back-merge PR into development/develop/dev so the fix isn't lost at the next release. Needs the GitHub CLI for GitHub repos. |
| release-pr | /release-pr [version] opens (or updates) a PR from development/develop/dev into main/master with release notes built from the merged PRs, grouped into features, bug fixes and maintenance, plus deploy heads-ups (migrations, config, dependencies) and a suggested version. Needs the GitHub CLI for GitHub repos. |
Copy a command's .md file to ~/.claude/commands/ (Windows: C:\Users\<you>\.claude\commands\) and
start a new Claude Code session.
Getting started
-
Download this repo:
git clone https://github.com/rene-poulsen/jean-claude.git, or use Code > Download ZIP on GitHub. -
Copy the skill folder you want into your Claude skills folder:
cp -r jean-claude/skills/my-week ~/.claude/skills/On Windows that folder is
C:\Users\<you>\.claude\skills\. You can also copy it in File Explorer. To use a skill in one project only, copy it to that project's.claude/skills/folder instead. -
Start a new Claude Code session. Use the skill by typing
/and its name (e.g./my-week), or just ask for what it does ("what did I do this week?").
Some skills need a one-time setup, such as installing a tool or creating an API key. It's in their README.
To update a skill, copy the new version over the old folder. Your settings (config.txt /
config.json) are only in your copy, so copy the new files in rather than deleting the folder first.
Repo layout
| Folder | Contents | Install to |
|---|---|---|
skills/ | One folder per skill: SKILL.md (instructions for Claude), README.md (for you) and any scripts | ~/.claude/skills/ |
commands/ | Slash commands (.md files) | ~/.claude/commands/ |
agents/ | Subagent definitions (.md files) | ~/.claude/agents/ |
hooks/ | Hook scripts and the settings.json snippets to wire them up | see each hook |