Add repo-specific repo assist map, MCP baseline verification, and project skills

[Copilot]

Pull Request

Description

Adds repo-specific guidance for agent runs in self-correcting-executor: a current repo map, dependency snapshot, MCP host/client/server framing, and a minimal live capability-negotiation proof. Also adds two project-scoped skills so CI debugging and repo summarization use this repo’s actual structure and workflows instead of generic examples.

• Repo assist doc

  • adds docs/REPO_MAP.md with:
    • focused tree map
    • mermaid architecture diagram
    • dependency summary from Python/CI/frontend manifests
    • agentic workflow checklist
    • MCP usage assessment and host/client/server mapping
    • live verification sequence for initialize, tools/list, and tools/call
    • CI baseline note calling out masked flake8 / pytest failures in current workflow behavior

• Project skills

  • adds .github/skills/github-actions-failure-debugging/SKILL.md
    • tailored to python-ci.yml and frontend-ci.yml
    • routes investigation through GitHub MCP workflow runs + job logs first
  • adds .github/skills/codebase-summary/SKILL.md
    • standardizes repo mapping, dependency review, and MCP baseline verification for this codebase

• Documentation wiring

  • updates README.md to point to the repo assist document

• Guardrail test

  • adds tests/test_repo_assist_docs.py to assert the new repo map sections and project skills remain present and repo-specific

from mcp_server.main import MCPServer

server = MCPServer()
await server.handle_request({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {"clientInfo": {"name": "repo-assist", "version": "1.0"}},
})

Type of change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (describe): project-scoped Copilot skills and focused documentation guardrail test

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable)

Additional context

The issue asked for repo-specific examples, at least two useful skills, and proof that baseline MCP negotiation works live for this repo. The new materials are intentionally scoped to the existing repository layout and workflows rather than introducing new runtime behavior.

• Fixes REPO UPDATE-> follow steps prove verification on implementation by running it live. #125

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: feac6b7b-83ae-4859-ba11-464b6df64d46

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}