Skip to content

Conversation

@dtannen
Copy link

@dtannen dtannen commented Aug 13, 2025

Hey,

I just built a website to host commands/agents/prompts, etc.

I imported your commands to commands.com. If you want to do it, I will delete the ones I imported. Happy for you to use your profile and get credit for it. You can use the commands.com MCP for yaml guidance, etc.

claude mcp add --transport http commands-com_mcp-server https://api.commands.com/mcp/commands-com/mcp-server

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 Welcome to the Claude Code Commands project,
@dtannen!

Thank you for opening your first pull request! We appreciate
your interest in contributing to our collection of slash commands.

📋 Community Guidelines

Before we proceed, please take a moment to review our
community standards:

🛡️ Community Values

We maintain a respectful, inclusive, and professional
environment
. Our community does not tolerate:

  • Hate speech, discrimination, or harassment
  • Personal attacks or inflammatory language
  • Spam, trolling, or off-topic content
  • Any content that violates our Code of Conduct

✅ What Makes a Great Pull Request

For Pull Requests:

  • Well-documented changes with clear descriptions
  • Following existing code style and conventions
  • Clear, descriptive commit messages
  • Addressing a specific issue or improvement
  • Including tests or examples where appropriate

🚀 Next Steps

A maintainer will review your pull request soon.
Please feel free to:

Thank you for helping make this project better! 🎉

- Added structured frontmatter to 39 tool commands and 14 workflow commands
- Includes name, description, allowed_tools, tags, category, version, and author fields
- Consistent formatting for commands.com import compatibility
- Preserved all existing command content and functionality

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@wshobson wshobson self-assigned this Aug 19, 2025
Copy link
Owner

@wshobson wshobson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technical Review

Thank you for your interest in this repository and for creating commands.com. After thoroughly reviewing this PR, I must decline it for the following technical reasons:

Changes Analysis

This PR adds:

  1. A 1,126-line commands.yaml manifest file
  2. YAML frontmatter metadata to all existing command files (adding ~17-20 lines per file)

Technical Assessment

No functional benefit: The changes are purely metadata additions that don't enhance the commands' functionality, fix bugs, or add features. The commands already work perfectly with Claude Code without this metadata layer.

Redundant information: The YAML frontmatter duplicates information already well-documented in the README. This violates DRY principles and creates maintenance overhead where changes would need to be synchronized in multiple places.

Unnecessary complexity: The commands.yaml file is essentially a catalog index that serves platform-specific needs rather than the repository's core purpose. Users of these commands don't need or benefit from this additional manifest file.

Maintenance burden: Future command additions or modifications would require updating both the markdown files and the YAML manifest, increasing the chance of inconsistencies and maintenance overhead without corresponding value.

Platform-specific coupling: These changes are tailored specifically for commands.com's ingestion format, which introduces unnecessary coupling to an external platform. The repository should remain platform-agnostic to serve its users best.

Recommendation

While I appreciate the work you've put into commands.com and the offer to host these commands, this PR doesn't align with the repository's goals of providing clean, maintainable slash commands for Claude Code users.

If you'd like to maintain a commands.com-compatible version, I'd suggest:

  • Maintaining your own fork with these platform-specific additions
  • Using a transformation script to generate the metadata from the existing files
  • Creating an integration that doesn't require modifying the source repository

The commands in this repository are designed to work directly with Claude Code's slash command system, and adding platform-specific metadata would not benefit the primary user base.

Thank you for your understanding.

@wshobson
Copy link
Owner

Closing this PR based on the technical review above. The proposed changes add platform-specific metadata without providing functional benefits to the repository or its users. Thank you for your interest in the project, and best of luck with commands.com!

@wshobson wshobson closed this Sep 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants