Modernize project structure and CI workflows

[kyhau]

Adopt python-repo-template best practices: update Makefile with comprehensive targets, switch to poetry-core, add black and flake8 for code quality, and move tests to the repo root. Overhaul GitHub Actions workflows (CI, Snyk, secrets scan, stale issues), improve dependabot config, and add cursor rules for development standards. Update README, LICENSE, and CHANGELOG to reflect new structure and tooling.

[amazon-q-developer]

⏳ Code review in progress. Analyzing for code quality issues and best practices. Detailed findings will be posted upon completion.

Using Amazon Q Developer for GitHub

Amazon Q Developer¹ is an AI-powered assistant that integrates directly into your GitHub workflow, enhancing your development process with intelligent features for code development, review, and transformation.

Slash Commands

Command	Description
/q <message>	Chat with the agent to ask questions or request revisions
/q review	Requests an Amazon Q powered code review
/q help	Displays usage information

Features

Agentic Chat
Enables interactive conversation with Amazon Q to ask questions about the pull request or request specific revisions. Use /q <message> in comment threads or the review body to engage with the agent directly.

Code Review
Analyzes pull requests for code quality, potential issues, and security concerns. Provides feedback and suggested fixes. Automatically triggered on new or reopened PRs (can be disabled for AWS registered installations), or manually with /q review slash command in a comment.

Customization

You can create project-specific rules for Amazon Q Developer to follow:

1. Create a .amazonq/rules folder in your project root.
2. Add Markdown files in this folder to define rules (e.g., cdk-rules.md).
3. Write detailed prompts in these files, such as coding standards or best practices.
4. Amazon Q Developer will automatically use these rules when generating code or providing assistance.

Example rule:

All Amazon S3 buckets must have encryption enabled, enforce SSL, and block public access.
All Amazon DynamoDB Streams tables must have encryption enabled.
All Amazon SNS topics must have encryption enabled and enforce SSL.
All Amazon SNS queues must enforce SSL.

Feedback

To provide feedback on Amazon Q Developer, create an issue in the Amazon Q Developer public repository.

For more detailed information, visit the Amazon Q for GitHub documentation.

Footnotes

1. Amazon Q Developer uses generative AI. You may need to verify generated code before using it in your environment. See the AWS Responsible AI Policy. ↩

[kyhau]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[amazon-q-developer]

Overall Assessment

This is an excellent modernization effort that brings the project up to current Python development standards. The changes demonstrate a comprehensive understanding of modern Python tooling and best practices.

✅ Strengths

Build System Modernization

• Successfully migrated from setuptools to poetry-core for cleaner, more modern builds
• Proper Poetry configuration with well-organized dependency groups
• Updated Python version support to include 3.10-3.13

Development Workflow Improvements

• Comprehensive Makefile with intuitive targets (setup-init, pre-commit, etc.)
• Added black for code formatting and improved linting setup
• Moved tests to repository root following modern conventions

CI/CD Enhancements

• Improved GitHub Actions workflows with better path filtering
• Added Snyk vulnerability scanning for enhanced security
• Enhanced dependabot configuration (removed redundant pip ecosystem)

Documentation & Project Structure

• Added comprehensive community files (CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md)
• Updated README with modern badges and clear installation instructions
• Added cursor rules for development workflow documentation

⚠️ Issues to Address

Security Concerns

• Command injection vulnerability in saml2aws_helper.py (high priority)
• Snyk action using @master instead of pinned version

Minor Improvements

• Missing Python 3.10 classifier in pyproject.toml
• Makefile dependency inconsistency for lint-python target
• CI concurrency configuration could be optimized
• Issue template links could be project-specific

🎯 Recommendation

Approve with minor fixes. The security vulnerability should be addressed before merging, but the overall modernization is well-executed and significantly improves the project's maintainability and developer experience.

The migration to Poetry, comprehensive Makefile, and enhanced CI/CD pipeline represent substantial improvements that will benefit long-term maintenance and contributor onboarding.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.45%. Comparing base (e604415) to head (d9b62ad).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #173      +/-   ##
==========================================
- Coverage   98.92%   95.45%   -3.47%     
==========================================
  Files           8        4       -4     
  Lines         926      220     -706     
==========================================
- Hits          916      210     -706     
  Misses         10       10              

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.