Vibe Index
🎯

reddit-fetch

🎯Skill

from ykdojo/claude-code-tips

VibeIndex|
What it does

reddit-fetch skill from ykdojo/claude-code-tips

πŸ“¦

Part of

ykdojo/claude-code-tips(7 items)

reddit-fetch

Installation

npm installInstall npm package
npm install -g cc-safe
npxRun with npx
npx cc-safe .
DockerRun with Docker
docker run --privileged
Local ServerRun MCP server locally
claude mcp add -s user playwright npx @playwright/mcp@latest
ConfigurationMCP configuration (may be incomplete)
{ "attribution": { "commit": "", "pr": "" } } ``` Setting both to e...
πŸ“– Extracted from docs: ykdojo/claude-code-tips
Need more details? View full documentation on GitHub β†’
10Installs
1,966
-
Last UpdatedJan 29, 2026
View on GitHubBack to Skills

Skill Details

SKILL.md

Overview

# 40+ Claude Code Tips: From Basics to Advanced

Here are my tips for getting the most out of Claude Code, including a custom status line script, cutting the system prompt in half, using Gemini CLI as Claude Code's minion, and Claude Code running itself in a container. Also includes the [dx plugin](#install-the-dx-plugin).

πŸ“Ί [Quick demo](https://www.youtube.com/watch?v=hiISl558JGE) - See some of these tips in action with a multi-Claude workflow and voice input:

[![Demo video thumbnail](assets/demo-thumbnail.png)](https://www.youtube.com/watch?v=hiISl558JGE)

Table of Contents

  • [Tip 0: Customize your status line](#tip-0-customize-your-status-line)
  • [Tip 1: Learn a few essential slash commands](#tip-1-learn-a-few-essential-slash-commands)
  • [Tip 2: Talk to Claude Code with your voice](#tip-2-talk-to-claude-code-with-your-voice)
  • [Tip 3: Break down large problems into smaller ones](#tip-3-break-down-large-problems-into-smaller-ones)
  • [Tip 4: Using Git and GitHub CLI like a pro](#tip-4-using-git-and-github-cli-like-a-pro)
  • [Tip 5: AI context is like milk; it's best served fresh and condensed!](#tip-5-ai-context-is-like-milk-its-best-served-fresh-and-condensed)
  • [Tip 6: Getting output out of your terminal](#tip-6-getting-output-out-of-your-terminal)
  • [Tip 7: Set up terminal aliases for quick access](#tip-7-set-up-terminal-aliases-for-quick-access)
  • [Tip 8: Proactively compact your context](#tip-8-proactively-compact-your-context)
  • [Tip 9: Complete the write-test cycle for autonomous tasks](#tip-9-complete-the-write-test-cycle-for-autonomous-tasks)
  • [Tip 10: Cmd+A and Ctrl+A are your friends](#tip-10-cmda-and-ctrla-are-your-friends)
  • [Tip 11: Use Gemini CLI as a fallback for blocked sites](#tip-11-use-gemini-cli-as-a-fallback-for-blocked-sites)
  • [Tip 12: Invest in your own workflow](#tip-12-invest-in-your-own-workflow)
  • [Tip 13: Search through your conversation history](#tip-13-search-through-your-conversation-history)
  • [Tip 14: Multitasking with terminal tabs](#tip-14-multitasking-with-terminal-tabs)
  • [Tip 15: Slim down the system prompt](#tip-15-slim-down-the-system-prompt)
  • [Tip 16: Git worktrees for parallel branch work](#tip-16-git-worktrees-for-parallel-branch-work)
  • [Tip 17: Manual exponential backoff for long-running jobs](#tip-17-manual-exponential-backoff-for-long-running-jobs)
  • [Tip 18: Claude Code as a writing assistant](#tip-18-claude-code-as-a-writing-assistant)
  • [Tip 19: Markdown is the s**t](#tip-19-markdown-is-the-st)
  • [Tip 20: Use Notion to preserve links when pasting](#tip-20-use-notion-to-preserve-links-when-pasting)
  • [Tip 21: Containers for long-running risky tasks](#tip-21-containers-for-long-running-risky-tasks)
  • [Tip 22: The best way to get better at using Claude Code is by using it](#tip-22-the-best-way-to-get-better-at-using-claude-code-is-by-using-it)
  • [Tip 23: Clone/fork and half-clone conversations](#tip-23-clonefork-and-half-clone-conversations)
  • [Tip 24: Use realpath to get absolute paths](#tip-24-use-realpath-to-get-absolute-paths)
  • [Tip 25: Understanding CLAUDE.md vs Skills vs Slash Commands vs Plugins](#tip-25-understanding-claudemd-vs-skills-vs-slash-commands-vs-plugins)
  • [Tip 26: Interactive PR reviews](#tip-26-interactive-pr-reviews)
  • [Tip 27: Claude Code as a research tool](#tip-27-claude-code-as-a-research-tool)
  • [Tip 28: Mastering different ways of verifying its output](#tip-28-mastering-different-ways-of-verifying-its-output)
  • [Tip 29: Claude Code as a DevOps engineer](#tip-29-claude-code-as-a-devops-engineer)
  • [Tip 30: Keep CLAUDE.md simple and concise](#tip-30-keep-claudemd-simple-and-concise)
  • [Tip 31: Claude Code as the universal interface](#tip-31-claude-code-as-the-universal-interface)
  • [Tip 32: It's all about choosing the right level of abstraction](#tip-32-its-all-about-choosing-the-right-level-of-abstraction)
  • [Tip 33: Audit your approved commands](#tip-33-audit-your-approved-commands)
  • [Tip 34: Write lots of tests (and use TDD)](

More from this repository6

πŸͺ
ykdojo-claude-code-tipsπŸͺMarketplace

40+ tips for getting the most out of Claude Code, from basics to advanced - includes a custom status line script, cutting the system prompt in half, using Gemini CLI as Claude Code's minion, and Claude Code running itself in a container. Also includes the dx plugin.

🎯
review-claudemd🎯Skill

Analyzes recent conversation history to identify improvements for CLAUDE.md files, suggesting rule reinforcements and new guidelines.

🎯
gha🎯Skill

Investigates GitHub Actions workflow failures by analyzing logs, run history, identifying root causes, and checking for potential fixes.

🎯
clone🎯Skill

Clones the current conversation, enabling users to explore alternative approaches without losing the original context.

🎯
handoff🎯Skill

Generates a comprehensive handoff document to ensure smooth knowledge transfer and continuity of work across different agents.

🎯
half-clone🎯Skill

Clones the latter half of the current conversation, reducing context while preserving recent work and token efficiency.