Claude Code Tips & Workflows
40+ practical tips for Claude Code, from basics to advanced, including a custom status line and containerized self-running demos.
- Source repo
- ykdojo/claude-code-tips
- Stars
- ★ 10k
- Last updated
- 24d ago
- License
- NOASSERTION
- Primary language
- HTML
- FA score
- 30/100 · Major gaps
At a glance
- How it runs
- Works with
- Platform-specificClaude Code
- Cost
- Free software; you pay for model usage
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- Developers looking to optimize context management in long Claude Code sessions can use the half-clone script to preserve recent work while reducing token usage.
- Not a fit if
- Teams not using Claude Code; the tips and scripts don't transfer to other AI coding tools
- Users wanting zero configuration; some scripts need hooks and CLAUDE.md setup
- Source review
- 30/100 · Major gaps 4 safety controls not found
What does this agent do, and when should you use it?
This repository by ykdojo compiles over 40 tips for mastering Claude Code, an AI coding assistant. It covers essential commands, voice input, context management, Git workflows, and testing strategies. The repo includes ready-to-use scripts and skills, such as a custom status line script (scripts/context-bar.sh), conversation trimming scripts, and the dx plugin that bundles everyday dev workflow skills. It also demonstrates how to run Claude Code inside a container for isolated, long-running autonomous tasks. These resources integrate via Claude Code's configuration mechanisms like CLAUDE.md, skills, and slash commands.
The repository provides scripts and skills that enhance Claude Code's terminal experience: 1) scripts/context-bar.sh customizes the status line to show model, directory, git branch, uncommitted file count, sync status, and token usage progress; 2) scripts/half-clone-conversation.sh trims a long conversation to keep only the latter half, tagging it with [HALF-CLONE] to reduce token consumption; 3) scripts/check-context.sh acts as a hook to automatically trigger /half-clone when context usage exceeds 85%; 4) skills/ folder includes handoff, gha, and review-claudemd skills for generating handoff documents, triaging GitHub Actions failures, and reviewing CLAUDE.md files. The dx plugin packages these skills for easy installation. Additionally, the repo demonstrates using tmux to control a containerized Claude Code instance, enabling autonomous remote operations.
- Developers looking to optimize context management in long Claude Code sessions can use the half-clone script to preserve recent work while reducing token usage.
- Teams frequently debugging GitHub Actions CI failures can leverage the /gha slash command to automatically investigate root causes and suggest fixes.
- Users juggling multiple parallel development tasks can adopt Git worktrees and a terminal tab cascade workflow to stay organized.
- Those needing to run Claude Code fully autonomously for long experiments can use Docker containers with --dangerously-skip-permissions.
- People who prefer voice input can follow the guide to set up local transcription tools like superwhisper, improving interaction speed.
How do you install or deploy this agent?
To install scripts and skills:
- Clone the repository:
git clone https://github.com/ykdojo/claude-code-tips - Copy desired scripts to ~/.claude/scripts/ and make them executable, e.g.:
cp scripts/context-bar.sh ~/.claude/scripts/
chmod +x ~/.claude/scripts/context-bar.sh- Symlink skills to ~/.claude/skills/, e.g.:
ln -s /path/to/repo/skills/handoff ~/.claude/skills/handoff- For the dx plugin, use
/pluginwithin Claude Code to install it.
How do you use this agent?
Configure the custom status line:
- Copy the script to local (e.g., ~/.claude/scripts/context-bar.sh) and ensure it's executable.
- Enable it in Claude Code settings or instruct Claude via CLAUDE.md.
- Run
claudeand observe the status line.
Use half-clone:
- In a long conversation, type
/half-cloneor run the script to trim to the latter half. - Alternatively, set up check-context.sh hook to trigger automatically when context exceeds 85%.
Use /gha skill:
- Type
/gha <GitHub Actions URL>in Claude Code; Claude investigates and suggests fixes.
Containerized run:
- Build or pull a container image with Claude Code, then run with
--dangerously-skip-permissions:
docker run --rm -it my-claude-image claude --dangerously-skip-permissionsWhat are this agent's strengths and limitations?
- Provides practical, ready-to-use scripts (status line, half-clone) that immediately improve Claude Code's usability.
- The dx plugin bundles multiple skills, streamlining installation and integration for daily dev workflows.
- Covers advanced patterns like containerized isolation and multi-model orchestration, showcasing Claude Code's flexibility.
- All tips and scripts are tailored specifically to Claude Code, not applicable to other AI coding tools.
- Some scripts require configuration (e.g., hooks) and may involve a learning curve to set up correctly.
- Advanced features like remote control or containerized execution may require additional dependencies or paid features.
How does this agent compare with similar options?
The repository does not provide direct comparisons with other AI coding tools, but it mentions using OpenAI Codex for code review, implying a multi-tool workflow where Claude Code orchestrates others.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Claude Code Tips & Workflows This agent | 30 · Major gaps | CLIFree + model costs | ★ 10k | 24d ago | HTML | Claude Code |
| elizaOS | 88 · Good | CLIFree + model costs | ★ 20k | 1d ago | TypeScript | — |
| Smart Ralph | 73 · Some gaps | Agent plugin / skillFree + model costs | ★ 559 | 1mo ago | Shell | Codex · Claude Code |
| Ring — Skills Library for AI Agents | 72 · Some gaps | Agent plugin / skillFree + model costs | ★ 217 | 5d ago | HTML | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows: README suggests configuring permissions (e.g., allow pull but not push) and mentions user review of PRs, reflecting least privilege and user confirmation practices. However, no specific information on data flow transparency, sensitive data handling, or dependency security. External effects: suggests using git and gh commands but does not explain potential risks. Rollback not mentioned. Source attribution: README explicitly mentions author ykdojo, but not verified. Deductions: lack of evidence for data flow transparency, sensitive data handling, dependency security, and rollback.
Evidence shows: README content is self-consistent, but no specific information on dependency availability or failure messages. Deductions: dependency availability and failure messages not mentioned.
Evidence shows: README targets Claude Code users, provides various usage scenarios and examples, but does not clearly define capability boundaries and trigger conditions. Environment fit: mentions Mac and Linux but not detailed. Deductions: insufficient information on capability boundaries, trigger precision, and environment fit.
Evidence shows: README has clear structure, table of contents, and multiple examples, but lacks installation instructions, known limitations, and version changelog. License is NOASSERTION, maintenance responsibility not clear. Deductions: missing installation notes, known limitations, version changelog, and unclear license.
Evidence shows: README provides many practical tips, output usability is high, marginal value is evident, but cost-benefit not quantified. Deductions: cost-benefit not provided with specific data.
Evidence shows: Claims in README are mostly personal experience, no verifiable evidence provided. Deductions: lack of cross-source corroboration and clear separation of facts and inferences.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: dependency securityPin versions and run a dependency audit (npm audit, pip-audit) before installing; prefer running it in a container.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- The repository lacks clear installation instructions; users need to explore on their own.
- License is NOASSERTION; confirm copyright and licensing terms before use.
- Dependency security is not mentioned; be cautious when using third-party tools.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
Refresh captured command outputs in Tip 1 (#70): /usage, /chrome, /mcp, /stats updated to current Claude Code (v2.1.250). Also includes the Ctrl+L shortcut fix and hooks doc link update from main.View on GitHub ↗ -
Release notes excerpt
Update outdated claims in the README (#69): Tip 8 context numbers and plan mode section, Tip 20 Opus phrasing, Tip 32 Remote Control default, Tip 33 artifact CDNs, Tip 36 subagent model default. Also includes Tip 49 (concise output style) from main.View on GitHub ↗ -
Release notes excerpt
- Fix half-clone project-dirname conversion for Windows paths (#67) - Verify #67 on a real Windows runner, escape the project path in the history.jsonl entry, and make TESTING.md a running review log (#68) Plugin version bumped to 0.14.27 (the half-clone script is bundled with the plugin).View on GitHub ↗