sjnims/plugin-dev

AI Summary: This issue requests adding a new section to the CONTRIBUTING.md file to guide contributors on shell script quality. It proposes including instructions on running `shellcheck`, handling intentional warnings with directives, and addressing common `shellcheck` issues. The goal is to ensure better shell script quality within the project.

AI Summary: This issue proposes adding a 'skills' field to the frontmatter of three agents (agent-creator, plugin-validator, skill-reviewer) to enable automatic loading of relevant skills. This will ensure agents have necessary context without manual intervention, improving their functionality and self-sufficiency.

AI Summary: This issue proposes minor documentation and consistency improvements for three subagents. The changes include aligning the `tools` field format with official documentation, adding explicit script paths for clarity, and documenting the rationale behind the model choice in the `agent-creator` agent. These are considered minor enhancements to improve developer experience and documentation accuracy.

AI Summary: Two agent markdown files, `agent-creator.md` and `skill-reviewer.md`, are missing opening code block markers (markdown) in their 'Output Format' sections. This causes the intended code templates to be rendered as regular markdown, hindering the agent's ability to correctly interpret and follow the output format.

AI Summary: This issue addresses inconsistencies in the YAML frontmatter of the `create-plugin.md` documentation. It identifies three specific areas for improvement: shortening the description, correctly formatting the `argument-hint` with brackets, and restricting the `allowed-tools` to be more specific, particularly for the Bash tool. The suggested improvements aim to align the documentation with Claude Code slash command best practices.

AI Summary: This issue requests adding documentation for the `allowed-tools` frontmatter field to the `plugin-structure` skill documentation. This field allows developers to restrict tool access for skills, and its absence makes the documentation incomplete. The suggested improvement includes a brief explanation and an example of how to use `allowed-tools` within the `SKILL.md` file.

AI Summary: This issue proposes removing an extraneous README.md file from the `plugin-structure` skill. The file is not part of the official Claude Code skill structure, creates a maintenance burden with outdated word counts, and duplicates information already present in SKILL.md. Removing it will bring the skill into conformance with documentation standards.

AI Summary: This documentation issue points out the incorrect use of second-person language ('you're') in the mcp-integration skill reference. The suggested fix involves rephrasing the instructional text to follow the skill writing style guidelines, which require an imperative or infinitive verb-first form.

AI Summary: This issue requests adding a reference to the `search-mcp-servers.sh` script within the `SKILL.md` documentation for the mcp-integration skill. The script is currently documented elsewhere but not easily discoverable from the main skill documentation, hindering user awareness of this utility.

AI Summary: This issue proposes adding documentation to the mcp-integration skill to guide users on discovering available MCP servers. Currently, users lack information on how to find relevant servers, leading to manual browsing and guesswork. The suggested improvement includes a new discovery reference file detailing the official registry, alternative sources, and category mappings for common plugin needs.

AI Summary: This issue proposes adding a new shell script, `search-mcp-servers.sh`, to the MCP integration skill. This script will enable programmatic discovery of MCP servers, addressing the current manual and tedious process. It will provide contextual search with popularity ranking based on GitHub stars, improving the developer experience for creating plugins.

AI Summary: The documentation for the `model` field in command development currently only shows shorthand values, but official documentation indicates that full model strings are also accepted. This issue proposes updating the `frontmatter-reference.md` file to clarify that both shorthand and full model IDs are valid inputs, explaining that shorthand uses the default version of each model family.

AI Summary: This issue requests documentation updates for the command-development skill to clarify the use of the `!` prefix for bash pre-execution in actual command files. The current documentation and examples omit this prefix, which needs to be explained to users.

AI Summary: This issue proposes adding documentation for the optional `allowed-tools` frontmatter field in the skill-development documentation. This field allows users to restrict the tools Claude can access when a skill is active, enhancing security and control for specific skill types. The proposed solution includes adding a new section to the `SKILL.md` file and updating the validation checklist.

AI Summary: This issue proposes adding an `examples/` directory to the `skill-development` skill within the `plugin-dev` project. This directory will contain templates for creating new skills, including a minimal example and a more complete structure, to improve consistency and user guidance.

AI Summary: This issue addresses two documentation gaps in the skill-development SKILL.md file. It proposes updating the validation checklist to include specific format rules for skill names and descriptions, and clarifying the purpose of two reference files to help users understand which to consult.

AI Summary: This issue addresses an inconsistency where the `validate-agent.sh` script incorrectly allows uppercase letters in agent names, contradicting the `SKILL.md` documentation which mandates lowercase, numbers, and hyphens only. The fix involves updating the script's regular expression to enforce lowercase validation and aligning the error message accordingly.

AI Summary: This issue proposes replacing a warning emoji (⚠️) in the SKILL.md file with plain text like 'Important' or 'Warning'. This change is to ensure consistency with project style guidelines that discourage the use of emojis in documentation unless explicitly requested.

AI Summary: This GitHub issue proposes adding a new utility script, `create-agent-skeleton.sh`, to the `scripts/` directory. This script will generate a template Markdown file for a new agent, including YAML frontmatter, a placeholder description, and a basic system prompt structure, thereby streamlining the agent development process.

AI Summary: This issue proposes adding new trigger phrases to the 'agent-development' skill's description to improve its discoverability for users asking comparative or conceptual questions about agents and skills. The goal is to ensure users can find the existing, informative content within the skill by matching common search queries.

AI Summary: This issue proposes adding cross-references within the agent-development skill's documentation to link users to related command-development and skill-development skills. The goal is to improve navigation and help users discover relevant information for understanding different component types.

AI Summary: This issue proposes several documentation improvements for the agent-development skill. Key changes include adding guidance on model selection, enriching the "Additional Resources" section with descriptions of reference files, clarifying the full script path in the workflow, and noting the difference between 'tools' and 'allowed-tools' fields for agents and skills respectively.

AI Summary: This issue proposes adding a new section to the `agent-development` skill documentation to clarify when to use agents, commands, or skills. It includes a comparison table and decision criteria to help users select the most appropriate component for their use case, aiming to reduce misuse and improve decision-making.

AI Summary: This issue addresses a documentation error where a non-existent script, `test-agent-trigger.sh`, is referenced in the `agent-development` skill documentation. The proposed fix is to remove the erroneous reference, ensuring documentation accuracy and preventing user confusion.

AI Summary: This issue proposes a refactoring effort to convert passive voice and second-person language in skill content to an imperative/infinitive form, aligning with best practices for skill development. The goal is to ensure all documentation uses objective, instructional language for clarity and consistency.