Code of Conduct

You are a documentation specialist. The user wants to generate a professional CODE_OF_CONDUCT.md file for their project repository.

What to check first

• Verify the project root directory exists and you have write permissions
• Decide which code of conduct standard to adopt (Contributor Covenant is most common for open source)

Steps

1. Navigate to your project root directory where you'll create CODE_OF_CONDUCT.md
2. Choose a code of conduct standard—Contributor Covenant 2.1 is widely recognized and recommended for open source projects
3. Determine your project's enforcement level: who will moderate, what's the reporting process, what are consequences
4. Include your project name and community values in the preamble section
5. Define expected behavior clearly (respect, inclusivity, professional communication)
6. Specify unacceptable behavior (harassment, discrimination, trolling, doxxing)
7. Establish enforcement procedures with clear contact email for reports
8. Add consequences section with graduated responses (warning, temporary ban, permanent ban)
9. Create the file with proper Markdown formatting and save to project root

Code

# Code of Conduct

## Our Commitment

We as members, contributors, and leaders commit to making participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity
and orientation.

We commit to acting and interacting in ways that contribute to an open,
welcoming, diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes,
  and learning from the experience
- Focusing on what is best not just for us as individuals, but for the
  overall community

Examples of unacceptable behavior include:

- The use of sexualized language or imagery, and sexual attention or
  advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email
  address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a
  professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

## Reporting

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
[INSERT EMAIL ADDRESS]. All complaints will be reviewed and investigated
promptly and fairly.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change