wanshuiyin

Contributing to Auto-claude-code-research-in-sleep (ARIS)

Development community intermediate

SOURCE https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep

Description

[English](CONTRIBUTING.md) | [中文版](CONTRIBUTING_CN.md) Thank you for your interest in contributing to ARIS! This document provides guidelines and instructions for contributing.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for wanshuiyin/Auto-claude-code-research-in-sleep, shared by 4 entries in this directory. It describes the repository, not this entry specifically.

Contributing to Auto-claude-code-research-in-sleep (ARIS)

[English](CONTRIBUTING.md) | [中文版](CONTRIBUTING_CN.md)

Thank you for your interest in contributing to ARIS! This document provides guidelines and instructions for contributing.

Ways to Contribute

Report bugs or issues
Suggest new features or skills
Improve documentation
Add translations
Share your use cases and feedback

Getting Started

Fork the repository

Clone your fork:

git clone https://github.com/YOUR_USERNAME/Auto-claude-code-research-in-sleep.git
cd Auto-claude-code-research-in-sleep

Create a branch for your changes:
```
git checkout -b your-feature-name
```

Development

Skill Development

Skills are Markdown files located in `skills/`. Each skill has:

Frontmatter: YAML metadata (name, description, allowed-tools)
Content: The skill instructions

Example skill structure:

---
name: my-skill
description: What this skill does
argument-hint: [optional-argument-hint]
allowed-tools: Read, Write, Bash(*)
---

# Skill Title

Instructions here...

Testing Your Changes

Before submitting:

Install your modified skill: cp -r skills/your-skill ~/.claude/skills/
Test in Claude Code: /your-skill test argument
Verify the skill works as expected

Pull Request Process

Make sure your changes are well-documented
Update README.md if you add new skills or features
Keep PRs focused on a single change
Write clear commit messages

PR Checklist

Code follows the project style
Documentation is updated (if applicable)
Changes are tested locally

Code of Conduct

Be respectful and inclusive
Focus on constructive feedback
Help others learn and grow

Questions?

Feel free to open an issue for any questions or join our WeChat group (QR code in README).

License

By contributing, you agree that your contributions will be licensed under the MIT License.