core: pre-commit

Author: simonprovost

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -121,7 +121,7 @@ body:
     id: tool-version
     attributes:
       label: "mcpstack-tool-builder Version"
-      description: What version are you using? If cloned, paste the commit SHA: `git rev-parse --short HEAD`.
+      description: What version are you using? If cloned, paste the commit SHA.
       placeholder: "e.g., 0.1.0"
     validations:
       required: true

CODE_OF_CONDUCT.md

@@ -131,4 +131,3 @@ For answers to common questions about this code of conduct, see the FAQ at
 [Mozilla CoC]: https://github.com/mozilla/diversity
 [FAQ]: https://www.contributor-covenant.org/faq
 [translations]: https://www.contributor-covenant.org/translations
-

SECURITY.md

@@ -13,18 +13,18 @@ Include the following information in your report:
 - **Description**: A clear explanation of the vulnerability, with reproduction steps if possible.
 - **Environment**: Operating system, Python version, MCP client, and any relevant setup details.
 
-Send reports to: **simon.gilbert.provost@gmail.com** 
+Send reports to: **simon.gilbert.provost@gmail.com**
 
 We will acknowledge receipt within 7 days and aim to provide a resolution or mitigation timeline within 30 days. Please do not share vulnerabilities publicly until a fix has been released.
 
 ## Scope and Considerations
 
-- **Tool Combinations**: MCPStack-Tool-Builder is designed to compose with other MCP tools. Unexpected or unsafe interactions between tools cannot be predicted or prevented at the MCPStack-Tool level. The responsibility for safe orchestration rests with the user.  
-- **Data Breach Risks**: MCPStack-Tool-Builder runs locally and does not send data to external services. There are no cloud communications by default, so conventional remote data breaches do not apply.  
+- **Tool Combinations**: MCPStack-Tool-Builder is designed to compose with other MCP tools. Unexpected or unsafe interactions between tools cannot be predicted or prevented at the MCPStack-Tool level. The responsibility for safe orchestration rests with the user.
+- **Data Breach Risks**: MCPStack-Tool-Builder runs locally and does not send data to external services. There are no cloud communications by default, so conventional remote data breaches do not apply.
 - **GitHub Issues and Pull Requests**: Do not upload sensitive data (such as private datasets, logs, or credentials) when filing issues or submitting pull requests. Use synthetic or anonymized examples instead.
 
 ## Good Practices
 
-- Keep dependencies updated.  
-- Test tool compositions in a controlled environment.  
-- Sanitize any shared examples when discussing issues publicly.
+- Keep dependencies updated.
+- Test tool compositions in a controlled environment.
+- Sanitize any shared examples when discussing issues publicly.