0 Fork 0

T

Let git ls-remote reach Gitea from the sandbox

Run git ls-remote unsandboxed so SSH works, and ask before each use like
the other network git commands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-21 00:06:42 +02:00

.claude

Let git ls-remote reach Gitea from the sandbox

2026-10-21 00:06:42 +02:00

src

Initial commit: demo todo CLI with Claude Code setup

2026-10-20 23:49:20 +02:00

test

Initial commit: demo todo CLI with Claude Code setup

2026-10-20 23:49:20 +02:00

.gitignore

Initial commit: demo todo CLI with Claude Code setup

2026-10-20 23:49:20 +02:00

CLAUDE.md

Initial commit: demo todo CLI with Claude Code setup

2026-10-20 23:49:20 +02:00

package.json

Initial commit: demo todo CLI with Claude Code setup

2026-10-20 23:49:20 +02:00

README.md

Initial commit: demo todo CLI with Claude Code setup

2026-10-20 23:49:20 +02:00

README.md

claude-playground

A tiny todo CLI that exists to try out Claude Code features.

npm test
npm start -- add "try Claude Code"
npm start -- done 1
npm start -- ls

What's set up

File	Claude Code feature
`CLAUDE.md`	Project memory, loaded into every session
`.claude/settings.json`	Shared permissions + a hook that syntax-checks `.js` files after every edit
`.claude/skills/changelog/`	A custom skill — run `/changelog`
`.claude/agents/test-writer.md`	A custom subagent — "use the test-writer agent to…"

Things to try

"There's a bug in how ids are assigned after removing a todo — find it and fix it with a test."
"Use the test-writer agent to cover src/todo.js."
"Add a --json flag to ls." then /code-review
/changelog after a few commits
Press shift+tab to cycle permission modes (e.g. plan mode before a bigger change)
/memory to edit CLAUDE.md, /agents and /hooks to inspect the setup