cleanup: remove obsolete git hooks infrastructure

[atxtechbro]

Summary

Remove obsolete git hooks infrastructure, applying Invest, Simplify, and Subtraction Creates Value principles.

Principles Applied

• ✅ Invest: Keep .githooks/ with core.hooksPath (modern, version-controlled approach)
• ✅ Simplify: Remove manual installation complexity and duplication
• ✅ Subtraction Creates Value: Delete obsolete code that no longer serves a purpose

Changes

Removed

• hooks/ directory (outdated pre-push hook from Aug 5)
• bin/install-git-hooks (obsolete manual installation script)

Why This Is Better

The .githooks/ + core.hooksPath approach (configured in setup.sh:613):

• ✅ Version controlled - hooks travel with the repo
• ✅ Automatic setup - no manual installation needed
• ✅ Single source of truth - no duplication
• ✅ Works in worktrees - consistent across all clones

Evolution Timeline

1. Aug 5, 2025 - Created hooks/ + bin/install-git-hooks during MCP experiment (issue Experiment: Test Claude Code without git/github MCP servers #1213)
2. Sept 4, 2025 - Fixed with .githooks/ + core.hooksPath configuration (issue fix: add pre-push hook to prevent accidental direct pushes to main #1300)
3. Today - Removing technical debt left from the experiment

What Remains Active

• .githooks/pre-commit - Validates Claude command synchronization
• .githooks/pre-push - Prevents direct pushes to main branch
• setup.sh - Automatically configures core.hooksPath on installation

Test Plan

• Verified git still uses .githooks/ (via git config --get core.hooksPath)
• Confirmed no documentation references to old approach
• Both active hooks tested and working
• 50 lines of obsolete code removed
• Clean diff - only removes intended files

Impact

• Code Quality: Single source of truth, no duplication
• Developer Experience: Automatic hook setup, no manual steps
• Maintenance: Less code to maintain, clearer structure

[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. ↩

[amazon-q-developer]

Review Summary

This is an excellent cleanup PR that successfully removes obsolete git hooks infrastructure while maintaining the modern, version-controlled approach. The changes align perfectly with the stated principles of Invest, Simplify, and Subtraction Creates Value.

Key Strengths

• Clear intent: The PR description thoroughly explains the evolution from manual installation to automated core.hooksPath configuration
• Safe removal: Only removes truly obsolete code - the modern .githooks/ directory and setup.sh configuration remain intact
• Well-documented: Excellent timeline showing the progression from experiment to final cleanup
• Zero risk: Pure deletion of unused files with no functional impact

Verification Completed

• ✅ Confirmed .githooks/pre-push exists and is more robust than the removed version
• ✅ Verified setup.sh line 613 properly configures core.hooksPath
• ✅ No references to removed files found in active codebase
• ✅ Modern approach provides superior developer experience

The removed files served their purpose during the MCP experiment but are now technical debt. This cleanup improves maintainability and reduces confusion for future contributors.

Recommendation: Approve and merge - this is exactly the kind of proactive maintenance that keeps codebases healthy.