Uh oh!
There was an error while loading. Please reload this page.
feat: Add global Amplifier access system - #7
Closed
Michael J. Jabbour (michaeljabbour) wants to merge 24 commits into
Closed
feat: Add global Amplifier access system#7Michael J. Jabbour (michaeljabbour) wants to merge 24 commits into
Michael J. Jabbour (michaeljabbour) wants to merge 24 commits into
Conversation
…imental portions out to separate repos/branches.
…ter support for new worktree names
* Fix worktree creation issues: VIRTUAL_ENV warning and verbose output - Remove parent shell's VIRTUAL_ENV to prevent mismatch warning - Add --quiet flag to suppress verbose package list (234 packages) - Pass clean environment to uv sync subprocess - Maintain all functionality with cleaner, more readable output 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Prevent worktree commands from running within worktrees Add detection to prevent create_worktree.py and remove_worktree.py from being run inside a worktree, which causes incorrect path construction. Changes: - Add ensure_not_in_worktree() function to both scripts - Detect worktree by comparing git-common-dir with git-dir - Show clear error message with exact command to run from main repo - Exit cleanly without attempting operations when in worktree This follows ruthless simplicity: detect and fail fast with clear guidance rather than attempting complex path resolution. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Enable self-removal of worktrees with 'make worktree-rm .' Allow users to remove the current worktree from within itself using 'make worktree-rm .' or 'make worktree-rm <current-branch-name>'. Changes: - Replace ensure_not_in_worktree() with is_in_worktree() check - Add get_worktree_info() to get current branch and main repo path - Handle special case when arg is '.' or matches current branch - Change to main repo before performing removal operations - Add clear warnings about directory deletion - Add safety checks for None values to satisfy type checker This improves UX by allowing users to clean up their worktree without navigating back to the main repo first. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
* fix: migrate to Pydantic v2 patterns and fix test warnings - Replace deprecated class Config with ConfigDict in Pydantic models - Replace json_encoders with @field_serializer for datetime serialization - Fix pytest warning by removing test function return value in favor of assertions - Update test_parallel_execution.py to use assertions instead of returning dict This eliminates all 7 warnings that were appearing during test runs: - 3 PydanticDeprecatedSince20 warnings for class-based config - 3 PydanticDeprecatedSince20 warnings for json_encoders - 1 PytestReturnNotNoneWarning for test function return value 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Merge branch 'main' of https://github.com/microsoft/amplifier into fix-tests
Completely removed the claude-web directory and all its dependencies from the project: - Deleted claude-web/ directory containing the web interface code - Removed claude-web dependency group from pyproject.toml (fastapi, uvicorn, etc.) - Removed claude-web from pyright exclude patterns in pyproject.toml - Removed claude-web make target from Makefile - Updated documentation to remove claude-web references - Regenerated uv.lock, removing 7 unnecessary packages The project now has no traces of the claude-web interface, simplifying the codebase and reducing dependencies. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Add a new Claude command that automates the creation of well-formatted git commits following conventional commit standards. The command handles pre-commit checks, staging, and generates appropriate commit messages. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Update the commit command documentation to: - Remove emoji formatting reference (using standard conventional format) - Add guidance on leveraging conversation history for richer commit messages - Emphasize using context to help future reviewers and AI tools understand the rationale and intent behind changes This enhancement helps create more informative commit messages that capture not just what changed, but why it changed, making the git history more valuable for future reference and analysis. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
* chore: remove slides tool module and all references Removed the entire amplifier/slides_tool module as it was identified for removal. This simplifies the codebase by eliminating ~4,500 lines of code that are no longer needed. Changes: - Removed amplifier/slides_tool/ directory (17 files) - Removed slides-related make targets from Makefile - Removed slides-exports optional dependency from pyproject.toml - Removed slides tool documentation (docs/AMPLIFIER_SLIDES_TOOL.md) - Simplified tests/conftest.py to remove slides-specific fixtures 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Merge branch 'main' of https://github.com/microsoft/amplifier into remove-slides-tool # Conflicts: # pyproject.toml
…crosoft#5) * chore: remove unused PostgreSQL and Azure database infrastructure Remove all PostgreSQL-related code and dependencies that were never actually used by the application. Analysis revealed that all modules use file-based storage (JSON/JSONL in .data/) rather than PostgreSQL. Changes: - Remove psycopg2-binary dependency - Delete unused db_setup module (connection, schema, setup) - Delete Azure PostgreSQL infrastructure scripts and Bicep templates - Remove DATABASE_URL configuration from .env.example - Remove 67 lines of unused Makefile targets (azure-*, *-db) - Delete PostgreSQL setup documentation - Add REMOVED_POSTGRESQL.md to document what was removed and why This aligns with the ruthless simplicity philosophy - removing ~1900 lines of unused complexity. All storage remains file-based as it always was. The knowledge system, memory system, and claude-web continue to function exactly as before. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Merge remote-tracking branch 'origin/main' into remove-postgres
…rity Major README refactoring based on user feedback to: - Emphasize Amplifier's unique tools and systems (worktrees, knowledge extraction) - Clarify .data directory is git-ignored with benefits of external storage - Generalize knowledge system beyond just articles to all documentation - Fix workflow examples to clarify they apply to user's own code - Add more complete agent listing with categories - Restore status line component details - Add note about tool-agnostic portability Also updated SUPPORT.md to clearly state no support is provided for this experimental project, and enhanced commit command docs with review steps.
Created dual help system to improve developer experience: - `make` (default) shows ~15 essential commands organized by category - `make help` shows all 40+ available commands comprehensively Default view now includes key knowledge base commands (update, query, viz, stats) and essential development tools while maintaining simplicity. Full help provides exhaustive documentation of all available make targets. This follows the ruthless simplicity principle - new users see essentials, power users can discover everything with `make help`.
🌍 Enable Amplifier's powerful AI agents and tools on any codebase, anywhere This major enhancement allows developers to harness Amplifier's 20+ specialized agents (zen-architect, bug-hunter, security-guardian, etc.) on any project without copying files or modifying existing repositories. ✨ New Features: - Global 'amplifier' command for system-wide access - Smart auto-detection of Amplifier installation location - Enhanced startup scripts with comprehensive error handling - Seamless integration with existing Claude workflows - Cross-platform compatibility (macOS, Linux, WSL) 🚀 Usage: make install-global # Install global command amplifier ~/my-project # Use Amplifier on any project amplifier --help # Show usage examples 📈 Benefits: - All 20+ specialized agents available on any codebase - Shared knowledge base across all projects - Same powerful automation and quality tools - Project isolation - changes only affect target project - No need to modify or copy files to existing projects 🔧 Implementation: - Enhanced amplifier-anywhere.sh with robust error handling - New bin/amplifier wrapper for global installation - Updated Makefile with install-global targets - Comprehensive documentation in README - Fixed Claude settings path resolution This democratizes access to Amplifier's AI development superpowers, making every codebase instantly compatible with the full Amplifier toolkit.
- Fix handling of Claude flags when no directory specified - Ensure --version flag works correctly without triggering full startup - Improve argument parsing logic to handle edge cases - Maintain backward compatibility with all usage patterns Tested scenarios: ✅ amplifier --version (shows version only) ✅ amplifier --print 'command' (uses current dir + Claude args) ✅ amplifier /path/to/project --model sonnet (explicit dir + args) ✅ amplifier /nonexistent/path (proper error handling) ✅ amplifier --help (shows help text)
- Modify .gitignore to permit bin/amplifier global command - Maintain exclusion of other build artifacts - Enable proper version control of global installation script
- Modified bin/amplifier to capture and pass the original PWD - Updated amplifier-anywhere.sh to use ORIGINAL_PWD when available - Fixes issue where 'amplifier' from any directory would default to amplifier repo instead of current dir
* chore: complete cleanup of removed dependencies - Remove unnecessary documentation file for PostgreSQL removal - Clean up unused dependencies from pyproject.toml - Update test package description to be generic - Update uv.lock to reflect dependency changes 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * feat: add comprehensive smoke test suite with enhanced visibility Implemented a lightweight smoke test system that validates all Makefile commands with minimal overhead. The test suite runs in under 2 minutes and provides clear visibility into what's being tested and validated. Key features: - 31 smoke tests covering all user-facing commands - Enhanced output visibility showing actual command output (2-3 lines) - Smart filtering to skip boilerplate and show meaningful content - Startup tests for heavy commands that verify processing begins - Context display showing where validation patterns are found - Clear pass/fail indicators with informative messages - No external test framework dependencies (uses Python stdlib + YAML) The implementation follows the ruthless simplicity philosophy: - Direct subprocess execution without complex abstractions - Simple YAML configuration for test definitions - Minimal validation that catches 90% of issues - Fast execution (< 2 minutes for full suite) Tests are divided into categories: - Basic commands (help, check, worktree operations) - Content commands (scan, search, status) - Knowledge commands (sync, search, export, events) - Graph commands (build, search, neighbors, export) - Heavy startup tests (verify processing begins within 10 seconds) The enhanced visibility improvements address user feedback by showing what commands actually output and what patterns are being validated, making it clear what each test is checking without overwhelming the observer with unnecessary details. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Merge branch 'main' of https://github.com/microsoft/amplifier into clean-up * fix: improve smoke test validation and remove unhelpful tests - Fixed Triage Test to create .md file instead of .txt (triage expects markdown) - Removed trivial AI Validation Example test that only echoed text - Fixed Help Command pattern to match 'QUICK START' (uppercase) - Added meaningful validation patterns for tests that only checked exit codes - Fixed Knowledge Events validation to match actual log output format - All 30 smoke tests now pass successfully Note: Content tests take 15-18s because they scan actual filesystem, which is expected behavior for content scanning operations. * fix: improve smoke test robustness and remove fragile environment-dependent tests - Remove Worktree List test that depended on specific branch names - Fix Content Scan validation to check for actual output patterns - Simplify Clean WSL Files test to only verify exit code (cleanup should be silent) - Remove year-specific checks from Knowledge Events test (fragile date dependencies) - Fix Run Tests validation to check for session start instead of PASSED/FAILED These changes make the smoke tests more reliable across different environments and reduce false failures from transient state dependencies. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * feat: implement AI-driven smoke test system with ruthless simplicity Replace complex regex-based smoke tests with AI evaluation approach: - Add model configuration system (fast/default/thinking categories) - Create AI-driven test runner that evaluates outputs like a human would - Use isolated test environments to prevent side effects - Simplify test definitions to just commands and success criteria - Remove brittle pattern matching and complex validation logic Key improvements: - Tests complete in ~11 seconds vs previous implementation - Gracefully handles unavailable AI (falls back to basic checks) - No regex patterns or hardcoded validation rules - Reduced from 400+ lines to modular components totaling 413 lines - Follows ruthless simplicity and modular design philosophies 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: update model versions to latest Claude releases - Fast: claude-3-5-haiku-20241022 (unchanged) - Default: claude-sonnet-4-20250514 (updated from claude-3-5-sonnet-20241022) - Thinking: claude-opus-4-1-20250805 (updated from claude-3-opus-20240229) Updates model configuration to use the latest Claude model versions as specified by the user. * fix: update smoke tests to use Claude Code SDK for AI evaluation - Replaced Anthropic API with Claude Code SDK for AI evaluation - Made test runner async to support SDK's async operations - Fixed empty pass statement to comply with stub checker - Tests now work within Claude Code environment using SDK - AI provides meaningful pass/fail evaluation for each test - Gracefully handles SDK unavailability outside Claude Code The smoke tests now use the same Claude Code SDK that's already working in the knowledge extraction system, providing consistent AI evaluation across the codebase. * test: add sample test data files for smoke testing - Add test_article.md with structured content for knowledge extraction testing - Add test_code.py with sample Python function for code processing testing - These files are used by the smoke test isolated environment - Provides consistent test data that won't change over time These test files replace the need to process production content during smoke tests, making tests more predictable and faster while still validating the core functionality works correctly. * fix: improve smoke test configuration and data handling - Create data subdirectory for amplifier data isolation - Only create sample files if they don't already exist (preserve test data) - Improve cleanup to only remove cache files, not test data - Add environment variables for model selection and AI skip behavior - Ensure test data directory uses absolute paths These changes make smoke tests more reliable and preserve test data between runs for easier debugging. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * test: add sample test data files for smoke testing - Add test_article.md with sample content about testing - Add test_code.py with simple Python functions - These files ensure smoke tests have data to work with * fix: resolve all smoke test failures and ensure test data integrity - Fix datetime arithmetic in test_parallel_execution.py by using timedelta instead of datetime.replace() - Update graph export to use GEXF format instead of unsupported JSON format - Handle node attributes properly for GEXF export compatibility - Add proper test data structure with knowledge extractions and events - Create workspace detection Makefile for smoke tests - All 19 smoke tests now pass successfully 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * chore: remove smoke test runtime data from git tracking Remove previously tracked runtime artifacts from .smoke_test_data/data/ and add the directory to .gitignore to prevent future tracking. These files (query logs, knowledge graphs, extractions) are generated during smoke test execution and should remain local-only. Previously tracked files removed: - .smoke_test_data/data/knowledge/events.jsonl - .smoke_test_data/data/knowledge/extractions.jsonl - .smoke_test_data/data/knowledge/graph.gexf - .smoke_test_data/data/knowledge/query_log.jsonl These runtime artifacts were inadvertently committed but are now properly excluded from version control while preserving test fixture files in the parent .smoke_test_data/ directory. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
ContributorAuthor
@microsoft-github-policy-service agree [company="Microsoft"] |
ContributorAuthor
@microsoft-github-policy-service agree |
1 similar comment
ContributorAuthor
@microsoft-github-policy-service agree |
) Relocate subagent log files from `.data/subagent-logs/` to `logs/subagent-logs/` for better separation of concerns. The logs directory is already gitignored and provides a more appropriate location for project-specific logging, keeping it separate from other data storage needs. - Remove centralized path configuration logic that was unused - Simplify implementation to always use project root's logs directory - Tested with actual subagent invocations to verify correct logging
Move subagent logs from project root logs/ directory to .claude/logs/subagent-logs/ to maintain consistency with other Claude Code hook logs (post_tool_use, session_start, stop_hook). This centralizes all Claude Code-related logging in one location. - Changed log directory path from logs/subagent-logs to .claude/logs/subagent-logs - Ensures all Claude Code hook logs are co-located for easier management
Remove experimental and duplicate code from ai_working that has been superseded by the main implementation. This includes: - Prototype knowledge integration code (duplicates main functionality) - SECURITY_AND_MOBILE.md (remote access planning doc, not implemented) Part of repository cleanup effort to reduce complexity following ruthless simplicity principle. Removed 900 lines of obsolete code.
…ence (microsoft#9) * feat: add resilient knowledge extraction with focused extractors and real-time progress Major improvements to the knowledge extraction pipeline: Resilient Processing: - Add graceful degradation for partial failures during extraction - Save partial results when some extractors fail (better than nothing) - Track per-processor status with JSON persistence - Enable selective retry of only failed processors - Add comprehensive error reporting at end of batch runs Focused Extraction: - Split extraction into 4 focused extractors running in parallel: - ConceptExtractor: Technical concepts, patterns, methodologies - RelationshipExtractor: Dependencies and connections - InsightExtractor: Actionable insights and best practices - PatternExtractor: Code patterns and implementations - Each extractor optimized for its specific knowledge type - Better extraction quality through specialized prompts Enhanced User Experience: - Add real-time progress indicators showing parallel extraction - Show which extractors are running vs completed (✓ 2/4 complete) - Display immediate notifications as extractors finish - Fix display glitches with proper line clearing - Remove redundant title lines in output - Add token-based truncation (80k tokens) replacing character limits Error Handling: - Provide clear timeout messages when SDK unavailable - Distinguish between "no data found" and "extraction failed" - Show extraction times for performance monitoring - Continue processing despite individual failures Philosophy: Implements "partial results have value" - a 4-hour batch completing with 80% success is better than early failure with 0% results. This aligns with the project's pragmatic approach to batch processing. Co-Authored-By: Claude <noreply@anthropic.com> * fix: add visible document classification step with clean progress output Previously, document classification was implemented but not visible during knowledge-sync processing, causing all documents to default to "general" type. This fix makes classification a visible processing step with clean, animated progress output matching other processors. Changes: - Add _classify_document method to resilient_miner.py with proper async handling - Implement animated spinner progress during classification (matching other extractors) - Update all focused extractors to accept document_type parameter - Change verbose logging from info to debug level to reduce output noise - Fix circular imports using TYPE_CHECKING - Add test file to verify clean classification output The classification now shows a clean animated spinner during processing and displays the document type without extra logging messages, improving user visibility into the knowledge extraction pipeline. * feat: enhance knowledge extraction with better output, persistence, and retry defaults Comprehensive improvements to the knowledge extraction system focused on reliability and user experience for processing large batches of articles (350+). Output Display Improvements: - Show clean parallel extraction progress with animated spinner - Display individual processor completions with counts and timing - Properly handle error messages on separate indented lines - Remove duplicate completion reporting between inner/outer scopes - Thread-safe output with proper line clearing Progress Persistence: - Save processing status after each article completes (not just at end) - Skip already-processed articles on restart with clear messages - Show pre-processing summary: "Processing 350 articles (247 complete, 12 partial, 91 unprocessed)" - Support incremental processing with full resume capability - Enable safe interruption with Ctrl+C without losing progress Retry Behavior Changes: - Changed default to retry partial failures (goal: get everything complete) - Added --skip-partial-failures flag for opting out of retry behavior - Deprecated --retry-partial flag (hidden but functional with warning) - Aligns with incremental processing philosophy - common case needs no flags These changes enable reliable unattended processing of large article batches, with the system naturally driving toward 100% completion while providing clear visibility into progress and the ability to resume from any interruption. * refactor: rename resilient_miner to article_processor and clean up for merge - Rename module from resilient_miner.py to article_processor.py for clarity - Rename class from ResilientKnowledgeMiner to ArticleProcessor - Remove deprecated --retry-partial flag and backwards compatibility code - Fix duplicate completion messages in output by removing redundant logging - Simplify CLI flag handling to use only --skip-partial-failures - Update all imports and references throughout the codebase The new naming better reflects the module's purpose of processing articles through various extractors. Removed technical debt from deprecated flags and fixed output formatting issues for cleaner user experience. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Merge remote-tracking branch 'origin/main' into knowledge-recovery
* refactor: extract trace-viewer into standalone package Moved trace_viewer module to separate repository (claude-trace-viewer) for independent distribution via PyPI/uvx. This separation follows the modular design philosophy, allowing the trace viewer to be used as a standalone tool. Changes: - Removed trace_viewer/ module (4,308 lines) - Removed Flask dependency (no longer needed) - Removed @mariozechner/claude-trace package from installation - Cleaned up references in .gitignore, .claude/settings.json, and Makefile - Removed trace-viewer make target The trace viewer will be published to PyPI shortly and will be installable via 'uvx claude-trace-viewer' or 'pip install claude-trace-viewer'. This refactoring reduces the amplifier codebase by ~4,300 lines and removes an unnecessary dependency, following the ruthless simplicity principle. 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> * docs: add .claude-trace log directory to .gitignore * Merge branch 'main' of https://github.com/microsoft/amplifier into move-trace-viewer
Michael J. Jabbour (michaeljabbour) added a commit
to michaeljabbour/amplifier
that referenced
this pull request
Sep 30, 2025
Complete comprehensive technical specification library with all 44 principles: **People (6 specs)** - #1 Small AI-first working groups - #2 Strategic human touchpoints only - #3 Prompt engineering as core skill - microsoft#4 Test-based verification over code review - microsoft#5 Conversation-driven development - microsoft#6 Human escape hatches always available **Process (13 specs)** - microsoft#7 Regenerate, don't edit - microsoft#8 Contract-first everything - microsoft#9 Tests as the quality gate - microsoft#10 Git as safety net - microsoft#11 Continuous validation with fast feedback - microsoft#12 Incremental processing as default - microsoft#13 Parallel exploration by default - microsoft#14 Context management as discipline - microsoft#15 Git-based everything - microsoft#16 Docs define, not describe - microsoft#17 Prompt versioning and testing - microsoft#18 Contract evolution with migration paths - microsoft#19 Cost and token budgeting **Technology (18 specs)** - microsoft#20 Self-modifying AI-first codebase - microsoft#21 Limited and domain-specific by design - microsoft#22 Layered virtualization - microsoft#23 Protected self-healing kernel - microsoft#24 Long-running agent processes - microsoft#25 Simple interfaces by design - microsoft#26 Stateless by default - microsoft#27 Disposable components everywhere - microsoft#28 CLI-first design - microsoft#29 Tool ecosystems as extensions - microsoft#30 Observability baked in - microsoft#31 Idempotency by design (reference) - microsoft#32 Error recovery patterns built in - microsoft#33 Graceful degradation by design - microsoft#34 Feature flags as deployment strategy - microsoft#35 Least-privilege automation - microsoft#36 Dependency pinning and security scanning - microsoft#37 Declarative over imperative **Governance (7 specs)** - microsoft#38 Access control and compliance - microsoft#39 Metrics and evaluation everywhere - microsoft#40 Knowledge stewardship and institutional memory - microsoft#41 Adaptive sandboxing with explicit approvals - microsoft#42 Data governance and privacy controls - microsoft#43 Model lifecycle management - microsoft#44 Self-serve recovery with known-good snapshots Each specification includes: - Plain-language definition - AI-first development rationale - 4-6 implementation approaches - 5 good/bad example pairs with working code - 6 related principles with relationships - 7 common pitfalls with examples - Tools organized by category - 12 actionable checklist items Statistics: - 44 specifications totaling ~10,000+ lines - 220+ good/bad code example pairs - 240+ implementation approaches - 300+ documented anti-patterns - 500+ tools and frameworks - 250+ cross-principle relationships Created through parallel AI agent execution demonstrating Principle microsoft#13 (Parallel Exploration by Default). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
TAKESHI KAWAI (synx-kawai) pushed a commit
to synx-kawai/amplifier
that referenced
this pull request
Oct 21, 2025
…al Amplifier access
Mollie Munoz (momuno) added a commit
to momuno/amplifier
that referenced
this pull request
Nov 20, 2025
… for v0.3.0 Created feature scope and sprint plan for v0.3.0 "Test Case + Basic Regeneration" focusing on template-based document regeneration with diff preview workflow. Convergence Session (2025-11-19): - Defined 5 must-have features for reliable doc regeneration - Created test case template for amplifier/README.md - Deferred 21 features to backlog (updated MASTER_BACKLOG to 57 items) - Captured convergence completion summary Sprint Planning (v0.3.0): - Sprint 8 (4 days): Template parser & manual regen command - Sprint 9 (3 days): Source context & structure preservation - Sprint 10 (3 days): Change detection & user confirmation - Integrated issues microsoft#4, microsoft#5, microsoft#6, microsoft#7 into sprint work Workflow Improvements: - Fixed convergence-architect to create all 4 required outputs - Fixed sprint-planner to use proper versioned directory structure - Added test case template creation to convergence Phase 3 - Added validation checklists to prevent incomplete workflows Test Case: - Created templates/amplifier_readme.json as primary test case - 9 sections covering real-world README structure - Will validate all v0.3.0 features against actual project 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Mollie Munoz (momuno) added a commit
to momuno/amplifier
that referenced
this pull request
Nov 21, 2025
Implement real-time progress feedback during document generation following TDD. Changes: - Add progress_callback parameter to ChunkedGenerator.generate() - Track and report timing for each section - Display section progress (e.g., [1/2] Generating: Overview) - Show source files being used per section - Display completion markers with timing (✓ Complete (3.2s)) - Integrate progress callbacks with regen-doc CLI Tests: - 9 new progress feedback tests (100% passing) - All backward compatible (callback is optional) - Full test coverage for callback functionality Sprint 9 Day 1 Status: ✅ Complete - Issue microsoft#7 (progress feedback) resolved - 60/60 Sprint 8 + Sprint 9 tests passing 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Brian Krabach (bkrabach)force-pushed
the
main
branch
from
December 8, 2025 22:22
490c8da to
4ecb35cCompareDiego Colombo (colombod) added a commit
to colombod/amplifier
that referenced
this pull request
Feb 2, 2026
Add ecosystem governance guidance to prevent duplication and encourage sustainable growth: - Add core principle microsoft#7: Check existing capabilities before building new - Add 'Before Building New Functionality' section with: - Discovery Workflow (4-step process to check MODULES.md first) - Impact comparison table showing benefits of reuse vs duplication - Visual decision framework flowchart - Specific guidance for AI assistants to consult catalog This ensures when users (or AI assistants) request new functionality, they first consult the Component Catalog (MODULES.md) to find existing solutions, consider extensions, or contribute back to the ecosystem. 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🌍 Global Amplifier Access
This PR introduces a comprehensive system for using Amplifier's specialized agents and tools on any project, anywhere on your system - not just within the Amplifier directory.
What's New
Global Command Installation
make install-globaltarget that installsamplifiercommand globallyUniversal Script System
amplifier-anywhere.sh- Core script for running Amplifier on any projectbin/amplifier- Global wrapper that finds your Amplifier installationEnhanced User Experience
Usage Examples
Key Benefits
✅ All 20+ specialized agents work on external projects
✅ Shared knowledge base - insights from one project help others
✅ Same powerful automation - quality checks, parallel development
✅ Project isolation - changes only affect your target project
✅ Works anywhere - no need to copy files or modify your projects
Files Changed
install-globaltargetInstallation Locations
The global
amplifiercommand automatically searches for Amplifier in:~/dev/amplifier(most common)~/amplifier~/repos/amplifier~/code/amplifier/opt/amplifierTemplate Usage
Users should start Claude sessions with:
Commits in this PR
This feature significantly expands Amplifier's utility by making it available system-wide while maintaining proper project isolation.