kata-make-clean-framework

Remove Ahrena-installed files via Makefile clean or install.py --clean.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-make-clean-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-make-clean-framework
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-make-clean-framework
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-make-clean-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably remove files installed by Ahrena without needing to manually locate what to delete or risk unintended changes.

Core Features & Use Cases

  • Targeted cleanup workflow: Uses either the Makefile clean target or the Ahrena installer --clean mode to remove installed artifacts.
  • Pre-flight verification: Checks codex-make guidance for the correct clean mechanism and verifies that .ahrena/install.py exists when using the equivalent approach.
  • Environment-aware execution: Determines the appropriate terminal type from .ahrena/.directives (or safely infers it) before running the cleanup command.

Quick Start

Ask the AI: "Run kata-make-clean-framework for this repository and confirm whether the clean step succeeds or explain exactly what failed."

Frequently Asked Questions about kata-make-clean-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove Ahrena-installed files from my repository?

To remove Ahrena-installed files, execute the `make clean` target or run `python .ahrena/install.py --clean`. The workflow checks codex-make guidance and verifies `.ahrena/install.py` availability to perform deterministic cleanup without manual confirmation.

What is the correct procedure to clean up Ahrena installation artifacts?

The correct procedure for cleaning Ahrena installation artifacts involves consulting codex-make for equivalence, validating the `.ahrena/install.py` script, and executing the cleanup command in the appropriate terminal. It returns command output with actionable failure diagnostics.

How do I run make clean for an Ahrena project without manual confirmation?

You can run `make clean` for an Ahrena project without confirmation by invoking the deterministic cleanup workflow. It automatically determines the appropriate terminal type from `.ahrena/.directives` and executes the removal of installed artifacts safely.

Does the Ahrena cleanup workflow verify the install script before removing files?

Yes, the Ahrena cleanup workflow verifies that `.ahrena/install.py` exists before attempting to remove files using the `--clean` mode. This pre-flight verification ensures the deterministic cleanup applies the correct mechanism without risking unintended changes.

Why does make clean fail to remove Ahrena-installed files and how do I fix it?

If `make clean` fails to remove Ahrena-installed files, the workflow provides actionable failure diagnostics in the command output. It checks codex-make guidance and validates `.ahrena/install.py` availability to help identify and resolve the cleanup issue.

Can I use python .ahrena/install.py --clean instead of make clean to remove artifacts?

Yes, you can use `python .ahrena/install.py --clean` instead of `make clean` to remove artifacts. The workflow consults codex-make for equivalence, ensuring either method achieves deterministic cleanup of Ahrena-installed files based on your project setup.