Support Atmos Pre-Commit Hooks

[RoseSecurity]

Describe the Feature

Support Atmos Pre-commit hooks for documentation generation, validation, linting, and whatever else your heart desires. Maybe something like:

repos:
  -   repo: https://github.com/cloudposse/atmos
      rev: v1.227.0
      hooks:
      -   id: atmos-generate-docs
      -   id: atmos-validate-components
      -   id: atmos-validate-stacks

Expected Behavior

No response

Use Case

No response

Describe Ideal Solution

# .pre-commit-hooks.yaml
- id: atmos-generate-docs
  name: Atmos Generate Documentation
  description: Generate component and stack documentation.
  entry: atmos docs generate readme
  language: golang
  pass_filenames: false


### Alternatives Considered

_No response_

### Additional Context

_No response_

[RoseSecurity]

I'll happily work on this if anyone's interested in this functionality

[osterman]

CodeRabbit (@coderabbitai) is it possible to maintain a library of precommit hooks in the atmos repo versioned along side atmos itself? what does it look like?

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '== Issue `#3023` =='
gh issue view 3023 --repo cloudposse/atmos --comments

echo
echo '== Candidate files =='
fd -HI -t f . | rg -i '(^|/)(pre-commit|precommit|hook|template|release|install|embed|go\.mod)(\.|/|$)' | head -n 250

echo
echo '== Relevant references =='
rg -n -i -C 2 '(pre-commit|precommit|git hook|hook library|template)' \
  -g '!vendor/**' -g '!**/node_modules/**' . | head -n 350

Length of output: 31660

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '== Command and installer outlines =='
ast-grep outline cmd/git/hooks/install.go --items all
ast-grep outline pkg/git/hooks/install.go --items all

echo
echo '== Command and installer source =='
cat -n cmd/git/hooks/install.go
cat -n pkg/git/hooks/install.go

echo
echo '== Repository pre-commit configuration =='
cat -n .pre-commit-config.yaml

echo
echo '== Pre-commit CI workflow =='
cat -n .github/workflows/pre-commit.yml

echo
echo '== Git hooks command documentation =='
sed -n '1,260p' website/docs/cli/commands/git/hooks/install.mdx

echo
echo '== Development hook documentation =='
sed -n '1,190p' docs/development.md

echo
echo '== Static asset embedding or release asset patterns =='
rg -n -C 2 '(go:embed|embed\.FS|Release.*Asset|release asset|ldflags|goreleaser)' \
  -g '*.go' -g '.goreleaser*' -g 'Makefile*' -g '*.yaml' -g '*.yml' . | head -n 260

Length of output: 46143

---

🏁 Script executed:

# Show the hook profiles and hooks embedded in this Atmos binary.
atmos git hooks library list

# Write a profile configuration to atmos.yaml.
atmos git hooks init --profile infrastructure

# Install the configured Git hook shims.
atmos git hooks install

# Run the configured hook set without creating a commit.
atmos git hooks run pre-commit

# Run hooks against all tracked files in CI.
atmos git hooks run pre-commit --all-files

Length of output: 939

---

🏁 Script executed:

atmos git hooks library list
atmos git hooks init --profile infrastructure

Length of output: 462

---

🏁 Script executed:

atmos git hooks install
atmos git hooks run <hook>

Length of output: 499

---

🏁 Script executed:

atmos git hooks run pre-commit

Length of output: 379

---

@osterman, this confirms only that the sandbox has no installed atmos binary.

No further command execution is needed. The design assessment is based on the checked source code: Atmos already has the Git-shim installer and hook runner needed for a versioned, embedded hook library.

You are interacting with an AI system.

[RoseSecurity]

I think it might follow a similar pattern to this

[osterman]

RoseSecurity that looks great; we could build it into our existing atmos git command name space.

[osterman]

RoseSecurity could you whip up a PRD? I'll review and once 👍 you can have a go at it.