refactor(*.md): unify md bold and colon formatting

Author: KemingHe

.github/ISSUE_TEMPLATE/bug-report.md

@@ -8,8 +8,8 @@ labels: 'bug, help wanted'
 
 ### 🐛 What happened?
 
-**Expected:** [What should happen]
-**Actual:** [What actually happened]
+**Expected**: [What should happen]
+**Actual**: [What actually happened]
 
 ### 🔄 Steps to Reproduce
 

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -15,14 +15,14 @@ Closes #[issue-number]
 
 ### 🎯 Key Features
 
-- **[Feature name]:** [Description of functionality or change]
+- **[Feature name]**: [Description of functionality or change]
 
 ### 💼 Business Impact
 
-- **[Impact area]:** [How this benefits users or business]
+- **[Impact area]**: [How this benefits users or business]
 
 ### 🔧 Technical Highlights
 
-- **[Technical aspect]:** [Implementation details or improvements]
+- **[Technical aspect]**: [Implementation details or improvements]
 
 ---

.github/workflows/README.md

@@ -16,15 +16,15 @@ graph TD
     ORCHESTRATOR --> UPDATE_DOCS
 ```
 
-**Security:** Pinned action hashes, signed commits, sequential execution
+**Security**: Pinned action hashes, signed commits, sequential execution
 
 ## 🚀 Planned Extensions
 
-- **Workflows:** `auto-update-index.yml` (Tantivy), `auto-build-and-deploy.yml` (Docker)
-- **Managers:** pipenv, pdm, pixi
-- **Features:** Conditional updates, performance monitoring
+- **Workflows**: `auto-update-index.yml` (Tantivy), `auto-build-and-deploy.yml` (Docker)
+- **Managers**: pipenv, pdm, pixi
+- **Features**: Conditional updates, performance monitoring
 
 ## 🔧 Operations
 
-- **Testing:** `workflow_dispatch` on both workflows  
-- **Monitoring:** Check Tuesday runs for upstream changes
+- **Testing**: `workflow_dispatch` on both workflows  
+- **Monitoring**: Check Tuesday runs for upstream changes

README.md

@@ -53,15 +53,15 @@ python-dep-manager-companion-mcp-server/
 
 ## 🛠️ Development
 
-**Transport Support:** Stdio (default) and HTTP modes following MCP standards.
+**Transport Support**: Stdio (default) and HTTP modes following MCP standards.
 
-**Environment Variables:**
+**Environment Variables**:
 
 - `TRANSPORT_MODE`: `stdio` or `http` (default: `stdio`)
 - `TRANSPORT_PORT`: HTTP server port (default: `8080`)
 - `TRANSPORT_HOST`: Host binding (default: `127.0.0.1`)
 
-**Local Development:**
+**Local Development**:
 
 ```shell
 # Clone and setup
@@ -73,7 +73,7 @@ uv sync
 uv run python src/server.py stdio
 ```
 
-**Roadmap:** Adding support for pipenv, pdm, pixi, and additional Python package managers.
+**Roadmap**: Adding support for pipenv, pdm, pixi, and additional Python package managers.
 
 ## 📄 License
 

prompts/prompt-commit-msg-gen.md

@@ -8,15 +8,15 @@ You are a senior software engineer creating conventional commit messages followi
 
 ### STEP 1: Repository Analysis (Machine)
 
-- **Local analysis:** Run `git status`, `git diff --staged`, `git log --oneline -10`
-- **Remote analysis:** Check `git log origin/main..HEAD` and recent branch activity
-- **MCP tools:** Use available MCP tools for codebase search, file reading, project analysis
+- **Local analysis**: Run `git status`, `git diff --staged`, `git log --oneline -10`
+- **Remote analysis**: Check `git log origin/main..HEAD` and recent branch activity
+- **MCP tools**: Use available MCP tools for codebase search, file reading, project analysis
 
 ### STEP 2: Classification & Title Generation (Machine)
 
-- **Change type:** Determine commit type (feat, fix, docs, style, refactor, test, chore, perf, ci, build)
-- **Scope:** Identify primary component (single word or hyphenated: api, auth, ui, workflow, user-auth)
-- **Title:** Generate imperative mood description (max 50 chars)
+- **Change type**: Determine commit type (feat, fix, docs, style, refactor, test, chore, perf, ci, build)
+- **Scope**: Identify primary component (single word or hyphenated: api, auth, ui, workflow, user-auth)
+- **Title**: Generate imperative mood description (max 50 chars)
 
 ### STEP 3: User Consultation (Human)
 
@@ -53,9 +53,9 @@ TECHNICAL NOTES
 
 ## CONSTRAINTS
 
-- **Title:** Max 50 characters, imperative mood ("add", "fix", "update")
-- **Content:** Only include sections with meaningful content, use dash bullets with no redundancy between items
-- **Issue linking:** Only include "closes #X" for actual issue resolution
+- **Title**: Max 50 characters, imperative mood ("add", "fix", "update")
+- **Content**: Only include sections with meaningful content, use dash bullets with no redundancy between items
+- **Issue linking**: Only include "closes #X" for actual issue resolution
 
 ## EXAMPLES
 

prompts/prompt-issue-gen.md

@@ -8,29 +8,29 @@ You are a technical documentation specialist creating GitHub issues that communi
 
 ### STEP 1: Information Gathering (Machine)
 
-- **Template discovery:** Search for bug-report.md, feature-request.md or check user-attached files
-- **Repository context:** Search codebase for related issues, recent changes, existing functionality
-- **Issue classification:** Analyze user input to determine bug report, feature request, or other type
-- **Content extraction:** Extract symptoms, desired functionality, technical requirements
+- **Template discovery**: Search for bug-report.md, feature-request.md or check user-attached files
+- **Repository context**: Search codebase for related issues, recent changes, existing functionality
+- **Issue classification**: Analyze user input to determine bug report, feature request, or other type
+- **Content extraction**: Extract symptoms, desired functionality, technical requirements
 
 ### STEP 2: User Consultation (Human + Machine)
 
-- **Template selection:** If type unclear, ask user to specify (Bug Report: problems/errors, Feature Request: new functionality)
-- **Context clarification:** Ask for missing template requirements (Bug: reproduction steps, expected/actual behavior, environment; Feature: problem statement, solution, alternatives)
-- **Priority assessment:** Confirm importance level and related issues/dependencies
+- **Template selection**: If type unclear, ask user to specify (Bug Report: problems/errors, Feature Request: new functionality)
+- **Context clarification**: Ask for missing template requirements (Bug: reproduction steps, expected/actual behavior, environment; Feature: problem statement, solution, alternatives)
+- **Priority assessment**: Confirm importance level and related issues/dependencies
 
 ### STEP 3: Issue Generation (Machine)
 
-- **Template compliance:** Follow discovered template structure with proper markdown formatting
-- **Information organization:** Structure content by template sections using dash bullets with clear, actionable details and no overlap between items
-- **Output delivery:** Present final issue in markdown code block with all required fields populated
+- **Template compliance**: Follow discovered template structure with proper markdown formatting
+- **Information organization**: Structure content by template sections using dash bullets with clear, actionable details and no overlap between items
+- **Output delivery**: Present final issue in markdown code block with all required fields populated
 
 ## CONSTRAINTS
 
-- **Template priority:** Use bug-report.md and feature-request.md as primary templates, adapt to any discovered templates
-- **Content accuracy:** Preserve technical details, error messages, requirements exactly as provided
-- **Actionable content:** Each section contains specific information that helps maintainers address the issue
-- **Label compliance:** Include appropriate labels and formatting per template frontmatter
+- **Template priority**: Use bug-report.md and feature-request.md as primary templates, adapt to any discovered templates
+- **Content accuracy**: Preserve technical details, error messages, requirements exactly as provided
+- **Actionable content**: Each section contains specific information that helps maintainers address the issue
+- **Label compliance**: Include appropriate labels and formatting per template frontmatter
 
 ## OUTPUT FORMAT
 

prompts/prompt-pull-request-gen.md

@@ -8,34 +8,34 @@ You are a senior software engineer creating pull request descriptions that commu
 
 ### STEP 1: Branch Analysis (Machine)
 
-- **Template discovery:** Search for pull_request_template.md or check user-attached files
-- **Git analysis:** Run `git log origin/main..HEAD --oneline`, `git diff origin/main...HEAD --stat`, `git show --name-only HEAD`
-- **Change analysis:** Use `git diff origin/main...HEAD` for code modifications and GitHub MCP tools for related issues/PRs
-- **Codebase context:** Search affected functionality, dependencies, and architectural patterns
+- **Template discovery**: Search for pull_request_template.md or check user-attached files
+- **Git analysis**: Run `git log origin/main..HEAD --oneline`, `git diff origin/main...HEAD --stat`, `git show --name-only HEAD`
+- **Change analysis**: Use `git diff origin/main...HEAD` for code modifications and GitHub MCP tools for related issues/PRs
+- **Codebase context**: Search affected functionality, dependencies, and architectural patterns
 
 ### STEP 2: User Consultation (Human + Machine)
 
-- **Change confirmation:** Present detected changes summary and confirm scope/key areas
-- **Issue linkage:** Ask which issues this resolves and related dependencies
-- **Context clarification:** Request business motivation, testing approach, breaking changes, review considerations
+- **Change confirmation**: Present detected changes summary and confirm scope/key areas
+- **Issue linkage**: Ask which issues this resolves and related dependencies
+- **Context clarification**: Request business motivation, testing approach, breaking changes, review considerations
 
 ### STEP 3: PR Generation (Machine)
 
-- **Template compliance:** Follow discovered template structure with proper markdown formatting
-- **Content organization:** Structure by template sections using dash bullets with no overlap, emphasizing business value and technical highlights
-- **Change categorization:** Group changes by:
-  - **Feature area:** Use when changes are specific to particular modules, functionality, or user-facing features
-  - **Impact level:** Apply when prioritizing by significance (critical fixes, performance improvements, minor updates)
-  - **Architectural component:** Choose for changes affecting core elements (database schemas, APIs, system integrations)
+- **Template compliance**: Follow discovered template structure with proper markdown formatting
+- **Content organization**: Structure by template sections using dash bullets with no overlap, emphasizing business value and technical highlights
+- **Change categorization**: Group changes by:
+  - **Feature area**: Use when changes are specific to particular modules, functionality, or user-facing features
+  - **Impact level**: Apply when prioritizing by significance (critical fixes, performance improvements, minor updates)
+  - **Architectural component**: Choose for changes affecting core elements (database schemas, APIs, system integrations)
   - These approaches can be combined for better clarity (e.g., feature area with impact level sub-grouping)
-- **Output delivery:** Present final PR description in markdown code block
+- **Output delivery**: Present final PR description in markdown code block
 
 ## CONSTRAINTS
 
-- **Template priority:** Use pull_request_template.md as primary template, adapt to any discovered templates
-- **Analysis depth:** Analyze feature branch against main using git commands and GitHub MCP tools
-- **Content accuracy:** Preserve implementation details, performance impacts, architectural decisions
-- **Business context:** Connect technical changes to business value and user impact
+- **Template priority**: Use pull_request_template.md as primary template, adapt to any discovered templates
+- **Analysis depth**: Analyze feature branch against main using git commands and GitHub MCP tools
+- **Content accuracy**: Preserve implementation details, performance impacts, architectural decisions
+- **Business context**: Connect technical changes to business value and user impact
 
 ## OUTPUT FORMAT
 

prompts/prompt-readme-gen.md

@@ -8,33 +8,33 @@ You are a technical documentation specialist creating comprehensive README files
 
 ### STEP 1: Project Analysis (Machine)
 
-- **Repository discovery:** Use readonly git commands (`git log --oneline -10`, `git branch -a`, `git ls-files`) to understand project history and structure
-- **Codebase analysis:** Use IDE editor/agent tools for file reading, directory traversal, and dependency analysis
-- **Structure mapping:** Run readonly bash commands (`find`, `ls -la`, `tree` if available) to map project architecture
-- **Technology detection:** Identify frameworks, languages, build tools, configuration files through file analysis
+- **Repository discovery**: Use readonly git commands (`git log --oneline -10`, `git branch -a`, `git ls-files`) to understand project history and structure
+- **Codebase analysis**: Use IDE editor/agent tools for file reading, directory traversal, and dependency analysis
+- **Structure mapping**: Run readonly bash commands (`find`, `ls -la`, `tree` if available) to map project architecture
+- **Technology detection**: Identify frameworks, languages, build tools, configuration files through file analysis
 
 ### STEP 2: User Consultation (Human + Machine)
 
-- **Project confirmation:** Present discovered project structure and technology stack for verification
-- **Purpose clarification:** Ask about project goals, target audience, key features, and unique value proposition
-- **Context gathering:** Request deployment details, environment requirements, known limitations, future roadmap
+- **Project confirmation**: Present discovered project structure and technology stack for verification
+- **Purpose clarification**: Ask about project goals, target audience, key features, and unique value proposition
+- **Context gathering**: Request deployment details, environment requirements, known limitations, future roadmap
 
 ### STEP 3: README Generation (Machine)
 
-- **Structure creation:** Generate file structure tree in plaintext code block with descriptive comments
-- **Content organization:** Create sections using level 2 headings with unique professional emojis, balance bullets and paragraphs to prevent both excessive bullets and oversized paragraphs
-- **Output delivery:** Present complete README in markdown code block ready for project root
+- **Structure creation**: Generate file structure tree in plaintext code block with descriptive comments
+- **Content organization**: Create sections using level 2 headings with unique professional emojis, balance bullets and paragraphs to prevent both excessive bullets and oversized paragraphs
+- **Output delivery**: Present complete README in markdown code block ready for project root
 
 ## CONSTRAINTS
 
-- **Technology agnostic:** Work with any programming language, framework, or project type
-- **Analysis depth:** Use only readonly commands and tools to understand project without modifications
-- **Section focus:** Include only essential sections applicable to both OSS and private projects
-- **Emoji standards:** Use unique professional emojis for level 2 headings only, no decorative elements
-- **Content simplicity:** Apply KISS (Keep It Simple, Stupid) and DRY (Don't Repeat Yourself) principles for concise and maintainable content
-- **Content balance:** Balance bullets and paragraphs to avoid excessive bullets or oversized paragraphs
-- **Content uniqueness:** Ensure no content overlap or repetition between sections
-- **Overview brevity:** Keep overview section under 10 seconds read time with essential value proposition only
+- **Technology agnostic**: Work with any programming language, framework, or project type
+- **Analysis depth**: Use only readonly commands and tools to understand project without modifications
+- **Section focus**: Include only essential sections applicable to both OSS and private projects
+- **Emoji standards**: Use unique professional emojis for level 2 headings only, no decorative elements
+- **Content simplicity**: Apply KISS (Keep It Simple, Stupid) and DRY (Don't Repeat Yourself) principles for concise and maintainable content
+- **Content balance**: Balance bullets and paragraphs to avoid excessive bullets or oversized paragraphs
+- **Content uniqueness**: Ensure no content overlap or repetition between sections
+- **Overview brevity**: Keep overview section under 10 seconds read time with essential value proposition only
 
 ## OUTPUT FORMAT