New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fix Log

by cloudposse in cloudposse/atmos

A skill your agent uses when implementing, finishing, documenting, or reviewing a fix, repair, remediation, bug fix, debug-and-fix task, workflow fix, infrastructure fix, or any change that should…

Apache-2.0Auto-check passedDevelopment

Install Fix Log

skills CLI
$ npx skills add cloudposse/atmos --skill fix-log -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cloudposse/atmos fix-log --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cloudposse/atmos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix-log .claude/skills/fix-log && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fix-log
GitHub stars
1.4k
Token cost
~685 tokens
SKILL.md length
319 words
Files
2 (incl. scripts)
Skills in repo
70
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when implementing, finishing, documenting, or reviewing a fix, repair, remediation, bug fix, debug-and-fix task, workflow fix, infrastructure fix, or any change that should…

  • Works in 6 steps: Before final ready status, create or… → Use the current local date for YYYY-MM-DD. → Use a lowercase slug with letters,… → …
  • Reviewing a fix
  • SKILL.md covers Workflow, Required Document Shape and Validation
  • Runs Shell scripts from its folder; calls bash

What it does

Fix Log is an agent skill from cloudposse/atmos. Use when implementing, finishing, documenting, or reviewing a fix, repair, remediation, bug fix, debug-and-fix task, workflow fix, infrastructure fix, or any change that should leave a durable fix record under docs/fixes.

Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/validate-fix-doc.sh`).

It sits in Development, covering Debugging. The repository describes itself as: Atmos is the open-source runtime for infrastructure — it builds, authenticates, and ships Terraform, OpenTofu, Packer, Ansible, Kubernetes, Helm, and containers the same way on… The licence is Apache-2.0.

When your agent uses it

  • Reviewing a fix
  • Debug-and-fix task
  • Infrastructure fix
  • Any change that should leave a durable fix record under docs/fixes

Example prompts

  • “/fix-log”

Requirements

  • A Bash shell

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Before final ready status, create or update docs/fixes/YYYY-MM-DD-.md.
  2. Use the current local date for YYYY-MM-DD.
  3. Use a lowercase slug with letters, numbers, and hyphens.
  4. Record what changed, why it changed, validation that actually ran, and follow-ups.
  5. Do not invent validation. If a check was skipped or blocked, say why.
  6. If the fix leaves any follow-up work (anything under Follow-ups other than None.), it must satisfy

What it can do on your machine

Read from SKILL.md and the folder at commit bbe58a6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fix Log loads about 685 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 319 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~685

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from cloudposse/atmos at commit bbe58a6, republished under its Apache-2.0 licence (© cloudposse). 319 words, ~685 tokens.

Download SKILL.mdSave it as .claude/skills/fix-log/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
fix-log
description
Use when implementing, finishing, documenting, or reviewing a fix, repair, remediation, bug fix, debug-and-fix task, workflow fix, infrastructure fix, or any change that should leave a durable fix record under docs/fixes.
metadata.copyright
Copyright Cloud Posse, LLC 2026
metadata.version
1.0.0

Fix Documentation

Every implemented fix must leave a short Markdown record in docs/fixes/.

docs/fixes/ already contains 90+ pre-existing records in an older, inconsistent format (some with a # Fix: <title> heading, some without; some with a **Date:** line, some without; and 25+ different ad hoc ## section names across the set — ## Problem, ## Root Cause, ## Tests, ## Related, etc.). Do not migrate those — they stay as-is. All new records use the merged format below, which keeps the old convention's most useful, scannable elements (the # Fix: heading, the explicit **Date:** line) and adopts a single, consistent five-section structure instead of ad hoc headers.

Workflow

  1. Before final ready status, create or update docs/fixes/YYYY-MM-DD-<slug>.md.
  2. Use the current local date for YYYY-MM-DD.
  3. Use a lowercase slug with letters, numbers, and hyphens.
  4. Record what changed, why it changed, validation that actually ran, and follow-ups.
  5. Do not invent validation. If a check was skipped or blocked, say why.
  6. If the fix leaves any follow-up work (anything under Follow-ups other than None.), it must satisfy CLAUDE.md's Follow-up Tracking (MANDATORY) section: open a GitHub issue and link it by number (e.g. #1234) in the Follow-ups section. A Follow-ups entry like "a follow-up will..." with no issue number is incomplete — the work will never be tracked.

Required Document Shape

markdown
# Fix: <Title>

**Date:** YYYY-MM-DD

## Summary

## Context

## Changes

## Validation

## Follow-ups
  • <Title> is a short human-readable description of the fix (inline code spans are fine, e.g. # Fix: `describe affected` now checks `source` and `provision` sections).
  • **Date:** restates the filename's date for at-a-glance scanning; keep it in sync with the filename.
  • Use None. in Follow-ups only when no follow-up is known.

Validation

After creating or updating fix docs, run:

bash
bash .claude/skills/fix-log/scripts/validate-fix-doc.sh docs/fixes/*.md

The validator only checks the five required ## sections and the filename shape — it doesn't (yet) enforce the # Fix: heading or **Date:** line. Run it against the files you're adding, not the whole directory indiscriminately (it will report errors against the old-format records, which is expected and not something to fix).

© cloudposse, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in .claude/skills/fix-log of cloudposse/atmos.

  • SKILL.md
  • scripts/validate-fix-doc.sh

Open the folder on GitHubat commit bbe58a6

Compare with similar skills

Fix Log next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fix Log compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix Log this skillcloudposse/atmos1.4k—~685Automated safety check: PassApache-2.0
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence
Herdr Throwaway Reproductionherdrdev/herdr43k—~2.4kAutomated safety check: PassApache-2.0
Systematic Debuggingultralisp/ultralisp25851 repos~2.4kAutomated safety check: PassNone

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes

  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed

  • Herdr Throwaway Reproduction

    herdrdev/herdr

    Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.

    43k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Systematic Debugging

    ultralisp/ultralisp

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    258 GitHub starsUsed in 51 repos~2.4k tokens
    DevelopmentAuto-check passed

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

More from cloudposse/atmos

All 70 skills in this repo

  • Atmos Lint

    cloudposse/atmos

    Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings.

    1.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Changelog

    cloudposse/atmos

    Blog post authoring for Atmos: MDX template, frontmatter, website/blog/tags.yml and authors.yml rules, problem-first framing, backtick-opening ban, optional cast embeds, and no-Go-internals leakage.

    1.4k GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Editions

    cloudposse/atmos

    Decide whether a PR's new or changed default needs edition-journal handling (pkg/edition, docs/prd/editions.md), and do the mechanical work if so: journal entries, the four-layer default check…

    1.4k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Atmos Migration

    cloudposse/atmos

    Migrate to Atmos from native Terraform, Terraform Workspaces, Terramate, Terragrunt, Make, Just, or Task; migrate tool versions from mise or Aqua CLI; migrate AWS/GCP/Azure CLI configs, Leapp…

    1.4k GitHub stars~5.1k tokensUpdated today
    Auto-check: warnings

  • PR Maintenance Loop

    cloudposse/atmos

    Start an hourly background loop that keeps the current branch's PR rebased, its addressed CodeRabbit threads resolved, its CI checks passing, its lint clean, its tests passing with adequate patch…

    1.4k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Roadmap

    cloudposse/atmos

    Maintain and update the Atmos roadmap page (website/src/data/roadmap.js): milestone/initiative/quarter schema, progress-percentage math, the curated featured[] cap (max 6, never auto-modified), and…

    1.4k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Fix Log

What does Fix Log do?

A skill your agent uses when implementing, finishing, documenting, or reviewing a fix, repair, remediation, bug fix, debug-and-fix task, workflow fix, infrastructure fix, or any change that should…. Fix Log is an agent skill from cloudposse/atmos. Use when implementing, finishing, documenting, or reviewing a fix, repair, remediation, bug fix, debug-and-fix task, workflow fix, infrastructure fix, or any change that should leave a durable fix record under docs/fixes.

When should I use Fix Log?

Fix Log fits situations like: reviewing a fix; debug-and-fix task; infrastructure fix; any change that should leave a durable fix record under docs/fixes.

How do I install Fix Log in Claude Code?

Run `npx skills add cloudposse/atmos --skill fix-log -a claude-code`. Or copy the skill folder (.claude/skills/fix-log in cloudposse/atmos) into .claude/skills/fix-log in your project. Claude Code loads it when a task matches its description.

How do I install Fix Log in Codex?

Run `npx skills add cloudposse/atmos --skill fix-log -a codex`. Or copy the skill folder (.claude/skills/fix-log in cloudposse/atmos) into .agents/skills/fix-log in your project. Codex loads it when a task matches its description.

Can I use Fix Log in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cloudposse/atmos --skill fix-log -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-log, .gemini/skills/fix-log, .github/skills/fix-log and .opencode/skills/fix-log in your project.

What does Fix Log need to run?

Going by SKILL.md and its folder, Fix Log needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.

Does Fix Log access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fix Log safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Fix Log use?

Fix Log is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fix Log use?

About 685 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fix Log?

Skills that share tags, products or a category with Fix Log: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Aoti Debug (pytorch/pytorch, 104k stars) and Herdr Throwaway Reproduction (herdrdev/herdr, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Log?

cloudposse (a GitHub organization) maintains it in cloudposse/atmos, which has 1,395 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 7, 2026.

Source: cloudposse/atmos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.