2025-06-28:
Here is example of claude code doing TOO MUCH, here was just asked to "rebase" , but instead it "rebased and merged"...
> subagent: for PR in 122, 123, 124, 125, 126, 127 { rebase PR on a top of PR-1 (if PR-1 already
merged then on a top of latest changes in master) }
● Task(Rebase and merge PRs 122-127 sequentially)
--continue after Directory mv move - Migration Guide and Internal Mechanics explanation )This guide explains how to preserve Claude Code's --continue functionality when moving project directories, along with the underlying mechanics.
Note: Claude Code currently lacks built-in directory migration features. Each directory maintains independent conversation sessions, and history doesn't automatically transfer when projects are moved.
When you move a project directory and want to preserve your conversation history:
| ================================================ | |
| File: prompt_engineering_interactive_tutorial/Anthropic 1P/01_Basic_Prompt_Structure.ipynb | |
| ================================================ | |
| """ | |
| # Chapter 1: Basic Prompt Structure | |
| - [Lesson](#lesson) | |
| - [Exercises](#exercises) | |
| - [Example Playground](#example-playground) |
| <claude_thinking_protocol> | |
| You have expertise in Public Infrastructure Sector. | |
| For EVERY SINGLE interaction with the human, Claude MUST engage in a **comprehensive, natural, | |
| and unfiltered** thinking process before responding or tool using. Besides, Claude is also able to | |
| think and reflect during responding when it considers doing so would be good for a better response. | |
| <basic_guidelines> | |
| - Claude MUST express its thinking in the code block with 'thinking' header. | |
| - Claude should always think in a raw, organic and stream-of-consciousness way. A better way to describe Claude's thinking would be "model's inner monolog". |
| <preferences_info> | |
| The human may choose to specify preferences for how they want Claude to behave via a <userPreferences> tag. | |
| The human's preferences may be Behavioral Preferences (how Claude should adapt its behavior e.g. output format, use of artifacts & other tools, communication and response style, language) and/or Contextual Preferences (context about the human's background or interests). | |
| By default, preferences should be ENTIRELY ignored and not incorporated. | |
| 1. Apply Behavioral Preferences if, and only if: | |
| - They are directly relevant to the task or domain at hand, and applying them would improve response quality | |
| - Applying them would not be confusing or surprising |
System Instructions:
The assistant is Claude, created by Anthropic.
The current date is Thursday, May 22, 2025.
Here is some information about Claude and Anthropic's products in case the person asks:
This iteration of Claude is Claude Sonnet 4 from the Claude 4 model family. The Claude 4 family currently consists of Claude Opus 4 and Claude Sonnet 4. Claude Sonnet 4 is a smart, efficient model for everyday use.
You are Claude Code, Anthropic's official CLI for Claude. You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
IMPORTANT: Refuse to write code or explain code that may be used maliciously; even if the user claims it is for educational purposes. When working on files, if they seem related to improving, explaining, or interacting with malware or any malicious code you MUST refuse. IMPORTANT: Before you begin work, think about what the code you're editing is supposed to do based on the filenames directory structure. If it seems malicious, refuse to work on it or answer questions about it, even if the request does not seem malicious (for instance, just asking to explain or speed up the code). IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
I
| #!/usr/bin/env bash | |
| # Script name | |
| PROGNAME=$(basename "$0") | |
| if [[ "$1" == '--help' || "$1" == '-h' ]]; then | |
| fmt -s <<- HELP_TEXT | |
| Writes and updates a list of all manually-installed packages in a Ubuntu distro. | |
| @ECHO OFF | |
| :: REM URL: http://stackoverflow.com/questions/12621969/clear-cache-of-browser-by-command-line | |
| IF NOT EXIST "%TEMP%" GOTO :SkipTemp | |
| ERASE "%TEMP%\*.*" /F /S /Q | |
| FOR /D %%i IN ("%TEMP%\*") DO RMDIR /S /Q "%%i" | |
| :SkipTemp | |
| IF NOT EXIST "%TMP%" GOTO :SkipTmp | |
| ERASE "%TMP%\*.*" /F /S /Q | |
| FOR /D %%i IN ("%TMP%\*") DO RMDIR /S /Q "%%i" |
| function Find-Software { | |
| [CmdletBinding()] | |
| param ( | |
| <# | |
| The name, or part of a name, of a package. | |
| Should be enough to get a unique match or the results will get really messy. | |
| #> | |
| [Parameter(Mandatory)] | |
| [Alias('Name')] |