Contributing to Fullstack Dev Skills Plugin

Contributing to Fullstack Dev Skills Plugin

Guidelines for contributing to this project.

How to Contribute

Reporting Issues

• Use GitHub Issues to report bugs or suggest features
• Check existing issues before creating a new one
• Provide detailed information:
  • Steps to reproduce (for bugs)
  • Expected vs actual behavior
  • Claude Code version
  • Relevant error messages or logs

Suggesting New Skills

When suggesting a new skill:

1. Explain the use case and target audience
2. Describe what the skill should do
3. List relevant technologies/frameworks
4. Provide examples of when it would be triggered

Adding Supported Agents

To add a new agent that implements the Agent Skills specification, see the [Supported Agents guide](docs/SUPPORTED_AGENTS.md#submit-a-new-agent) for submission instructions and PR template.

Submitting Changes

1. Fork and Clone

# Fork on GitHub, then:
git clone https://github.com/jeffallan/claude-skills.git
cd claude-skills

2. Create a Branch

git checkout -b feature/your-feature-name
# or
git checkout -b fix/your-bug-fix

3. Make Your Changes

**For New Skills:**

# Create skill directory
mkdir -p skills/my-new-skill

# Create SKILL.md following the structure below

4. Test Your Changes

# Copy skills to test location
cp -r skills/* ~/.claude/skills/

# Restart Claude Code and test
# Verify your skill activates correctly
# Test all examples in the SKILL.md

4.5. Validate Your Skill

Run the validation script to catch issues before CI:

python scripts/validate-skills.py --skill your-skill-name

5. Commit Your Changes

git add .
git commit -m "Add: My New Skill for XYZ framework"

**Commit Message Format:**

• Add: for new features/skills
• Fix: for bug fixes
• Update: for improvements to existing content
• Docs: for documentation changes
• Refactor: for code restructuring

6. Push and Create Pull Request

git push origin feature/your-feature-name

Then create a Pull Request on GitHub with:

• Clear title describing the change
• Description of what changed and why
• Any relevant issue numbers (e.g., "Fixes #123")

Linting & Formatting

This is a polyglot repo. All formatting is enforced via pre-commit hooks and CI.

Setup

pip install pre-commit
pre-commit install

Hooks run automatically on `git commit`. To run manually:

pre-commit run --all-files

# Or use Make targets:
make lint      # Check all formatting (Python, JS/TS, Markdown, Astro)
make format    # Auto-fix all formatting
make validate  # Run skill validation, markdown checks, and docs sync

Conventions

Language	Linter	Formatter	Config	Scope
Python	ruff	ruff-format	ruff.toml	scripts/*.py
Python	pyright	—	pyrightconfig.json	scripts/*.py
JS/TS/CSS	—	prettier	.prettierrc	site/,