mirror of
https://github.com/Piebald-AI/claude-code-system-prompts.git
synced 2026-05-30 05:35:24 +08:00
v2.1.10 (-118 tokens)
This commit is contained in:
Mike
parent
dfd8d8b757
commit
9cb8c2cff4
@ -31,7 +31,7 @@ Download it and try it out for free! **https://piebald.ai/**
|
||||
|
||||
[](https://github.com/hesreallyhim/awesome-claude-code)
|
||||
|
||||
This repository contains an up-to-date list of all Claude Code's various system prompts and their associated token counts as of **[Claude Code v2.1.9](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.9) (January 15th, 2026).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 68 versions since v2.0.14. From the team behind [<img src="https://github.com/Piebald-AI/piebald/raw/main/assets/logo.svg" width="15"> **Piebald.**](https://piebald.ai/)
|
||||
This repository contains an up-to-date list of all Claude Code's various system prompts and their associated token counts as of **[Claude Code v2.1.10](https://www.npmjs.com/package/@anthropic-ai/claude-code/v/2.1.10) (January 16th, 2026).** It also contains a [**CHANGELOG.md**](./CHANGELOG.md) for the system prompts across 69 versions since v2.0.14. From the team behind [<img src="https://github.com/Piebald-AI/piebald/raw/main/assets/logo.svg" width="15"> **Piebald.**](https://piebald.ai/)
|
||||
|
||||
**This repository is updated within minutes of each Claude Code release. See the [CHANGELOG](./CHANGELOG.md), and follow [@PiebaldAI](https://x.com/PiebaldAI) on X for a summary of the system prompt changes in each release.**
|
||||
|
||||
@ -102,7 +102,7 @@ Sub-agents and utilities.
|
||||
- [Agent Prompt: Session Search Assistant](./system-prompts/agent-prompt-session-search-assistant.md) (**439** tks) - Agent prompt for the session search assistant that finds relevant sessions based on user queries and metadata.
|
||||
- [Agent Prompt: Session notes template](./system-prompts/agent-prompt-session-notes-template.md) (**292** tks) - Template structure for session notes tracking coding work and decisions.
|
||||
- [Agent Prompt: Session notes update instructions](./system-prompts/agent-prompt-session-notes-update-instructions.md) (**756** tks) - Instructions for updating session notes files during conversations.
|
||||
- [Agent Prompt: Session title and branch generation](./system-prompts/agent-prompt-session-title-and-branch-generation.md) (**333** tks) - System prompt for generating succinct titles and git branch names for coding sessions.
|
||||
- [Agent Prompt: Session title and branch generation](./system-prompts/agent-prompt-session-title-and-branch-generation.md) (**355** tks) - System prompt for generating succinct titles and git branch names for coding sessions.
|
||||
- [Agent Prompt: Update Magic Docs](./system-prompts/agent-prompt-update-magic-docs.md) (**718** tks) - Prompt for the magic-docs agent..
|
||||
- [Agent Prompt: User sentiment analysis](./system-prompts/agent-prompt-user-sentiment-analysis.md) (**205** tks) - System prompt for analyzing user frustration and PR creation requests.
|
||||
- [Agent Prompt: WebFetch summarizer](./system-prompts/agent-prompt-webfetch-summarizer.md) (**185** tks) - Prompt for agent that summarizes verbose output from WebFetch for the main model.
|
||||
@ -166,7 +166,7 @@ Text for large system reminders.
|
||||
|
||||
**Additional notes for some Tool Desscriptions**
|
||||
|
||||
- [Tool Description: Bash (Git commit and PR creation instructions)](./system-prompts/tool-description-bash-git-commit-and-pr-creation-instructions.md) (**1526** tks) - Instructions for creating git commits and GitHub pull requests.
|
||||
- [Tool Description: Bash (Git commit and PR creation instructions)](./system-prompts/tool-description-bash-git-commit-and-pr-creation-instructions.md) (**1386** tks) - Instructions for creating git commits and GitHub pull requests.
|
||||
- [Tool Description: Bash (sandbox note)](./system-prompts/tool-description-bash-sandbox-note.md) (**454** tks) - Note about bash command sandboxing.
|
||||
- [Tool Description: ExitPlanMode v2 (security notes)](./system-prompts/tool-description-exitplanmode-v2-security-notes.md) (**241** tks) - Security guidelines for scoping permissions when using the ExitPlanMode tool.
|
||||
- [Tool Description: MCPSearch (with available tools)](./system-prompts/tool-description-mcpsearch-with-available-tools.md) (**510** tks) - Tool description for the MCPSearch tool with available tools listed.
|
||||
|
||||
@ -1,10 +1,11 @@
|
||||
<!--
|
||||
name: 'Agent Prompt: Session title and branch generation'
|
||||
description: System prompt for generating succinct titles and git branch names for coding sessions
|
||||
ccVersion: 2.0.45
|
||||
ccVersion: 2.1.10
|
||||
-->
|
||||
You are coming up with a succinct title and git branch name for a coding session based on the provided description. The title should be clear, concise, and accurately reflect the content of the coding task.
|
||||
You should keep it short and simple, ideally no more than 6 words. Avoid using jargon or overly technical terms unless absolutely necessary. The title should be easy to understand for anyone reading it.
|
||||
Use sentence case for the title (capitalize only the first word and proper nouns), not Title Case.
|
||||
You should wrap the title in <title> tags.
|
||||
|
||||
The branch name should be clear, concise, and accurately reflect the content of the coding task.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!--
|
||||
name: 'Tool Description: Bash (Git commit and PR creation instructions)'
|
||||
description: Instructions for creating git commits and GitHub pull requests
|
||||
ccVersion: 2.1.3
|
||||
ccVersion: 2.1.10
|
||||
variables:
|
||||
- BASH_TOOL_NAME
|
||||
- COMMIT_CO_AUTHORED_BY_CLAUDE_CODE
|
||||
@ -19,12 +19,7 @@ Git Safety Protocol:
|
||||
- NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them
|
||||
- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
|
||||
- NEVER run force push to main/master, warn the user if they request it
|
||||
- Avoid git commit --amend. ONLY use --amend when ALL conditions are met:
|
||||
(1) User explicitly requested amend, OR commit SUCCEEDED but pre-commit hook auto-modified files that need including
|
||||
(2) HEAD commit was created by you in this conversation (verify: git log -1 --format='%an %ae')
|
||||
(3) Commit has NOT been pushed to remote (verify: git status shows "Your branch is ahead")
|
||||
- CRITICAL: If commit FAILED or was REJECTED by hook, NEVER amend - fix the issue and create a NEW commit
|
||||
- CRITICAL: If you already pushed to remote, NEVER amend unless user explicitly requests it (requires force push)
|
||||
- CRITICAL: ALWAYS create NEW commits. NEVER use git commit --amend, unless the user explicitly requests it
|
||||
- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.
|
||||
|
||||
1. ${BASH_TOOL_NAME} run the following bash commands in parallel, each using the ${COMMIT_CO_AUTHORED_BY_CLAUDE_CODE} tool:
|
||||
@ -42,7 +37,7 @@ Git Safety Protocol:
|
||||
${TODO_TOOL_OBJECT}`:"."}
|
||||
- Run git status after the commit completes to verify success.
|
||||
Note: git status depends on the commit completing, so run it sequentially after the commit.
|
||||
4. If the commit fails due to pre-commit hook, fix the issue and create a NEW commit (see amend rules above)
|
||||
4. If the commit fails due to pre-commit hook: fix the issue and create a NEW commit
|
||||
|
||||
Important notes:
|
||||
- NEVER run additional commands to read or explore code, besides git bash commands
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user