Mystic Library

English

日本語

English

日本語

Appearance

Claude Dev System Prompt (PowerShell) ​

Intended Use ​

  • Standardize agent operating rules for Windows / PowerShell environments
  • Reduce command failures caused by shell differences

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.
- Be aware that the execution environment is PowerShell.
- When chaining commands, use ';' instead of '&&' because '&&' cannot be used in PowerShell.

# Git Command Execution Environment

- Execution environment: PowerShell
- Command chaining: use ';' (example: 'command1; command2; command3')

# 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. Integrate it while preserving PowerShell-specific execution rules.
  2. If used together with the Unix version, switch by environment.
  3. Adjust Git rules to match team standards.

Input Example ​

text
Environment: Windows 11 / PowerShell 7
Workflow: PR-based development
Note: Use `;` instead of `&&`

Output Example ​

text
PowerShell-compatible command execution policy and commit workflow rules

Notes ​

  • If the execution environment is not PowerShell, it may contain incompatible instructions.
  • Align auto-commit style instructions with your organization's approval process.