@benyue1978/soloflow-mcp
Version:
A Model Context Protocol (MCP) server for project document management with 32 comprehensive prompts covering the complete software development lifecycle
33 lines (24 loc) • 986 B
JavaScript
// Embedded git_commit.mdc content
export const GIT_COMMIT_MDC_CONTENT = `---
description: git commit rule
globs:
alwaysApply: false
---
# Git Usage
- Use the following **prefixes** for commit messages, followed by a **colon** and a **space**:
- \`fix\` — for bug fixes
- \`feat\` — for new features
- \`perf\` — for performance improvements
- \`docs\` — for documentation changes
- \`style\` — for formatting changes
- \`refactor\` — for code refactoring
- \`test\` — for adding missing tests
- \`chore\` — for routine tasks
- When determining the commit message prefix, pick the most **relevant** option from the list above.
- Use **lowercase** for all commit messages.
- Use **English** for all commit messages.
- If the change is not self-explanatory, include a **bullet list of changes** after a blank line below the summary.
- Commit but not push. You can only push after my approval.
---
`;
//# sourceMappingURL=git-commit-content.js.map