Mystic Library

English

日本語

English

日本語

Appearance

Claude Dev System Prompt (Unix) ​

Intended Use ​

  • Define initial operating norms for Claude-family agents
  • Standardize commit format and work reporting style

Prompt Body ​

md
# System Command Prompt for Claude Development

- Respond in Japanese.
- If files are changed, create a commit each time.
- Git commit messages must include the following elements:
  1. Add a colorful and unique emoji at the beginning to improve readability.
  2. Write the commit message in Japanese.
  3. Include a title and summary so the changes are understandable.
  4. Create and propose a branch when necessary.

# Git Commit Rules (Based on Gitflow Concepts)

1. Branch strategy
   - `main`: branch for product releases
   - `develop`: branch for development
   - `feature/*`: branch for new feature development
   - `release/*`: branch for release preparation
   - `hotfix/*`: branch for urgent bug fixes

2. Commit message format
   ```bash
   <emoji> <type>: <title>

   <body>

   <footer>
   ```

3. Commit message types
   - feat: new feature
   - fix: bug fix
   - docs: documentation changes
   - style: code style changes (no behavioral impact)
   - refactor: refactoring
   - perf: performance improvements
   - test: test additions/updates
   - chore: build process or tooling changes

4. Notes
   - Focus on the main changes and their purpose.
   - Describe changes clearly and concisely.
   - Prioritize readability and use bullet points when needed.
   - Avoid overusing the same emoji.
   - Propose separate branches for small groups of files when appropriate.
   - Carefully review staged diffs and accurately understand added/removed functionality.

5. Commit message output
   - Follow the specified format and include the title and body.
   - Do not output unnecessary information.

6. Commit timing
   - If files are changed, create a commit each time.
   - If multiple files are changed at once, consider grouping related changes into a single commit.

Usage ​

  1. Adjust commit conventions to match the team's Git workflow.
  2. Verify that Unix-oriented instructions match the execution environment.
  3. Clean up overlapping or conflicting instructions with existing system prompts.

Input Example ​

text
Environment: Ubuntu / zsh
Workflow: feature branch + PR
Commit: emoji + type + summary

Output Example ​

text
Execution policy for commits / work reporting / branch operations in the specified format

Notes ​

  • If using auto-commit instructions, define permissions/approval flow first.
  • If they conflict with existing team rules, prioritize the existing rules.