devscontext 0.1.0__tar.gz

devscontext-0.1.0/.claude/settings.local.json

@@ -0,0 +1,12 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(mkdir:*)",
+      "Bash(ruff check:*)",
+      "Bash(pytest:*)",
+      "Bash(ruff format:*)",
+      "Bash(python3 -m pytest:*)",
+      "Bash(python3 -m mypy:*)"
+    ]
+  }
+}

devscontext-0.1.0/.devscontext.yaml.example

@@ -0,0 +1,29 @@
+# DevsContext Configuration
+# Copy this file to .devscontext.yaml and configure your adapters.
+# API tokens should be set via environment variables for security.
+
+adapters:
+  jira:
+    enabled: true
+    base_url: "https://your-company.atlassian.net"
+    email: "${JIRA_EMAIL}"
+    api_token: "${JIRA_API_TOKEN}"
+
+  fireflies:
+    enabled: false
+    api_key: "${FIREFLIES_API_KEY}"
+
+  local_docs:
+    enabled: true
+    paths:
+      - "./docs"
+      - "./CLAUDE.md"
+
+synthesis:
+  provider: "anthropic"  # anthropic, openai, or ollama
+  model: "claude-3-haiku-20240307"
+  # api_key: "${ANTHROPIC_API_KEY}"  # Uses ANTHROPIC_API_KEY env var by default
+
+cache:
+  ttl_seconds: 300
+  max_size: 100

devscontext-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,38 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Lint with ruff
+        run: |
+          ruff check .
+          ruff format --check .
+
+      - name: Type check with mypy
+        run: mypy src/
+
+      - name: Run tests
+        run: pytest tests/ --ignore=tests/test_integration.py

devscontext-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,45 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build dependencies
+        run: pip install build
+
+      - name: Build package
+        run: python -m build
+
+      - name: Upload dist
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Download dist
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

devscontext-0.1.0/.gitignore

@@ -0,0 +1,211 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# DevsContext specific
+.devscontext.yaml
+.devscontext/

devscontext-0.1.0/CLAUDE.md

@@ -0,0 +1,129 @@
+**IMPORTANT: DevsContext is the product we are building. The payments-service, PROJ-1234, webhook examples, and other sample data in docs/example/ and tests/fixtures/ are SAMPLE DATA for testing — do NOT implement them. We are building the MCP server tool, not the example application.**
+
+# DevsContext
+
+## What is this?
+DevsContext is an open-source MCP server (Python) that provides AI coding agents
+with synthesized engineering context from SDLC tools (Jira, Fireflies, local docs).
+
+When a developer asks their AI agent to work on a task, DevsContext fetches relevant
+data on-demand from connected sources, synthesizes it via LLM into a structured
+context block, and returns it through MCP.
+
+## Architecture
+- MCP server using the official Python MCP SDK (`mcp` package)
+- On-demand fetching with optional pre-processing agent
+- Sources: Jira REST API, Fireflies GraphQL API, Slack, Gmail, local markdown docs
+- Synthesis: LLM (Claude Haiku / GPT-4o-mini / Ollama) combines raw data into structured block
+- Cache: in-memory TTL cache + optional SQLite for pre-built context
+
+### Plugin System
+Source adapters and synthesis engines are plugins.
+- Plugin interfaces defined in src/devscontext/plugins/base.py
+- Built-in plugins: jira, fireflies, slack, gmail, local_docs
+- External plugins: discovered via Python entry points (devscontext.plugins)
+- Plugins are activated by being listed in .devscontext.yaml
+
+### Pre-processing Agent
+- Watches Jira for tickets entering a configurable status (default: "Ready for Development")
+- Runs a multi-step pipeline: deep fetch → broad search → thorough matching → multi-pass synthesis
+- Stores pre-built context in SQLite (.devscontext/cache.db)
+- MCP server checks pre-built storage first, falls back to on-demand if not found
+- Agent and MCP server are separate processes sharing the same SQLite file
+
+### Fetch Strategy
+Primary source (Jira) fetched first, then all secondary sources in parallel.
+Each source plugin declares if it needs primary context via a needs_primary_context flag.
+
+### Optional RAG
+Disabled by default. When enabled via config, enhances local doc matching
+with embedding-based semantic search. Requires: pip install devscontext[rag]
+Index built manually: devscontext index-docs
+
+### Tool Behaviors
+- `get_task_context`: Full LLM synthesis, cached
+- `search_context`: No LLM, no cache (fast freeform search)
+- `get_standards`: No LLM, no cache (direct doc retrieval)
+
+## Tech Stack
+- Python 3.11+
+- `mcp` - MCP Python SDK for server implementation
+- `httpx` - async HTTP client for API calls
+- `click` - CLI framework
+- `pyyaml` - config parsing
+- `pydantic` - data validation and models
+- `aiosqlite` - async SQLite for pre-built context storage
+
+### Optional Dependencies
+All heavy deps are optional. Core install remains lightweight.
+- `anthropic` / `openai` - LLM clients for synthesis
+- `slack_sdk` - pip install devscontext[slack]
+- `google-api-python-client` - pip install devscontext[gmail]
+- `sentence-transformers` - pip install devscontext[rag]
+
+## Code Style
+- Use async/await for all I/O operations
+- Type hints on all function signatures
+- Pydantic models for data structures (adapters return typed models, not dicts)
+- Follow standard Python conventions (PEP 8, snake_case)
+- Keep functions small and focused
+- Error handling: never crash the MCP server - catch exceptions in adapters,
+  return partial context if a source fails
+- Logging: use `logging` module, structured log messages
+
+## Project Structure
+- `src/devscontext/server.py` - MCP server setup and tool registration
+- `src/devscontext/core.py` - main orchestration (fetch -> extract -> synthesize -> return)
+- `src/devscontext/adapters/` - one file per source (jira.py, fireflies.py, slack.py, gmail.py, local_docs.py)
+- `src/devscontext/plugins/` - plugin system (base.py, registry.py, synthesis.py)
+- `src/devscontext/rag/` - optional RAG support (embeddings.py, index.py)
+- `src/devscontext/synthesis.py` - LLM synthesis prompt and client
+- `src/devscontext/cache.py` - in-memory TTL cache
+- `src/devscontext/storage.py` - SQLite storage for pre-built context
+- `src/devscontext/preprocessor.py` - pre-processing agent
+- `src/devscontext/watcher.py` - Jira status watcher for agent
+- `src/devscontext/config.py` - YAML config loading and validation
+- `src/devscontext/cli.py` - CLI commands (init, test, serve, agent)
+- `src/devscontext/utils.py` - text utilities (keyword extraction, truncation)
+
+## MCP Tools (3 total)
+1. `get_task_context(task_id: str)` - full synthesized context for a Jira ticket
+2. `search_context(query: str)` - search across all sources by keyword
+3. `get_standards(area: str | None)` - coding standards, optionally filtered
+
+## Key Design Decisions
+- On-demand fetching with optional pre-processing for instant retrieval
+- No external vector DB - use NumPy + cosine similarity for optional RAG
+- LLM synthesis happens at retrieval time (or pre-built by agent)
+- Config via `.devscontext.yaml` in project root
+- Auth credentials via environment variables only (never in config file)
+- Graceful degradation: if a source is not configured, skip it and return available context
+- Plugin architecture: adapters and synthesis engines are extensible
+
+### Local Docs Matching
+Local docs are matched to tickets via:
+1. Components → doc filenames and headings
+2. Labels → doc filenames and headings
+3. Keywords from ticket title → doc content
+4. Standards docs (CLAUDE.md, .cursorrules, standards/) are always included
+
+Docs are classified by path:
+- `architecture/`, `arch/` → architecture docs
+- `standards/`, `style/`, `coding/` → coding standards
+- `adr/`, `adrs/` → architecture decision records
+- `CLAUDE.md`, `.cursorrules` → standards (special files)
+
+## Testing
+- Use pytest with pytest-asyncio
+- Mock external APIs in tests (httpx mock)
+- Test the synthesis prompt with fixture data
+
+## Commands
+- `devscontext init` - create .devscontext.yaml interactively
+- `devscontext test` - fetch a sample ticket and show synthesized output
+- `devscontext serve` - start MCP server (stdio transport)
+- `devscontext agent start` - start pre-processing agent (watches Jira)
+- `devscontext agent run-once` - process all matching tickets once
+- `devscontext agent status` - show agent and storage status
+- `devscontext agent process TICKET-123` - process a specific ticket
+- `devscontext index-docs` - build RAG index for local docs (requires [rag])

devscontext-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,112 @@
+# Contributing to DevsContext
+
+## Development Setup
+
+```bash
+git clone https://github.com/Pro0f/devscontext.git
+cd devscontext
+python -m venv venv
+source venv/bin/activate
+pip install -e ".[dev]"
+```
+
+Configure for local testing:
+```bash
+cp .devscontext.yaml.example .devscontext.yaml
+# Edit .devscontext.yaml with your Jira URL
+export JIRA_EMAIL="you@company.com"
+export JIRA_API_TOKEN="your-token"
+```
+
+## Running Tests
+
+Unit tests (no API keys needed):
+```bash
+pytest tests/ --ignore=tests/test_integration.py
+```
+
+Integration tests (requires real API keys):
+```bash
+pytest tests/test_integration.py
+```
+
+## Adding a New Adapter
+
+1. **Create adapter file** `src/devscontext/adapters/your_source.py`:
+   - Extend the `Adapter` base class from `plugins/base.py`
+   - Set class attributes: `name`, `source_type`, `config_schema`
+   - Implement required methods:
+     - `fetch_task_context(task_id, ticket=None) -> SourceContext`
+     - `search(query, max_results) -> list[SearchResult]`
+     - `health_check() -> bool`
+   - Optionally implement `close()` and `format_for_synthesis()`
+
+2. **Add config model** to `src/devscontext/models.py`:
+   - Create Pydantic model with `enabled`, `primary` fields
+   - Add to `SourcesConfig`
+
+3. **Register in plugin registry** `src/devscontext/plugins/registry.py`:
+   - Add to `register_builtin_plugins()` method
+   - Add loading logic in `load_from_config()`
+
+4. **Add tests** in `tests/test_your_source.py`
+
+See `adapters/slack.py` as a complete reference for communication sources.
+
+For full details, see [docs/plugins.md](docs/plugins.md).
+
+## Plugin Development
+
+DevsContext uses a plugin system for extensibility:
+
+- **Adapters**: Fetch context from data sources
+- **Synthesis Plugins**: Process and combine context
+
+External plugins can be published as pip packages using entry points.
+See [docs/plugins.md](docs/plugins.md) for the complete guide.
+
+## Testing Adapters
+
+```bash
+# Unit tests (no API keys needed)
+pytest tests/test_your_source.py
+
+# Test with real API (integration)
+devscontext test --task YOUR-123
+```
+
+## Testing Pre-processing Agent
+
+```bash
+# Process a single ticket
+devscontext agent process TEST-123
+
+# Check storage status
+devscontext agent status
+```
+
+## Code Quality
+
+Before submitting:
+```bash
+ruff check .
+ruff format .
+mypy src/
+pytest tests/ --ignore=tests/test_integration.py
+```
+
+Requirements:
+- Type hints on all functions
+- Pydantic models for data structures
+- Tests for new functionality
+
+## Pull Requests
+
+1. Fork and create a branch from `main`
+2. Make your changes with tests
+3. Ensure all checks pass
+4. Open a PR describing what and why
+
+## Questions?
+
+Open an issue.

devscontext-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Anthropic
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.