Skip to content
Back to skills

Discard

ASecurity

Use when a staged proposal doesn't warrant promotion, or was ticked reject in REVIEW.md Step 3, to remove the proposed staging directory without touching the live contextualizer.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
ai-agentsgobash

Works with

  • cli

Security analysis

A93/100
  • highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned September 6, 2026

npx -y skills add nick-railsback/skill-engine --skill discard --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Discard?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Discard
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nick-railsback-discard/badge)](https://www.skillsdirectory.com/skills/nick-railsback-discard)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: discard
description: Use when a staged proposal doesn't warrant promotion, or was ticked reject in REVIEW.md Step 3, to remove the proposed staging directory without touching the live contextualizer.
---

# Discard

Remove a proposed staging directory. The live contextualizer is not modified. Idempotent — discarding a non-existent proposed dir exits cleanly with a one-line diagnostic.

## When to invoke

Invoke `/skill-engine:discard <name>` when reviewing a proposal that does not warrant promotion — the predictions in Step 1 of `REVIEW.md` and the disagreement set in Step 2 surface enough divergence that re-running DISCOVER with a `--hint=...` is the right next move, not promotion. `discard` is also the path out when the user ticked `[x] reject` in Step 3: `/skill-engine:apply` refuses to promote a rejected proposal and points the user here.

## Resolving `<name>` and `<install>`

Same resolution as `/skill-engine:review`. See `review/SKILL.md` § Resolving `<name>`.

## Pre-discard prompt

Before removing anything, render a one-line confirmation naming the path:

```
Remove <install>/<name>-context.proposed/ (and its .review/ audit trail)? The live <name>-context/ is untouched. [y/N]
```

Accept `y` or `yes` (case-insensitive, leading/trailing whitespace trimmed) as consent. Treat `N`, blank input, or anything else as decline — the prompt is a single-shot, no re-prompt.

On decline, exit cleanly with:

```
Discard cancelled. <install>/<name>-context.proposed/ is untouched.
```

## The removal

On consent:

```bash
rm -rf "<install>/<name>-context.proposed/"
```

Exit message:

```
Removed <install>/<name>-context.proposed/. Live <name>-context/ is untouched.
```

## Idempotent paths

When the proposed dir does not exist at the resolved path (e.g., a stale invocation after an earlier discard, or a slug typo that resolves nowhere), surface:

```
No proposed staging dir at <install>/<name>-context.proposed/. Nothing to discard.
```

Exit zero (not an error condition — discarding nothing is a no-op).

When bare invocation finds zero `*-context.proposed/` directories under `<install>`, same shape:

```
No proposed staging dirs found under <install>. Nothing to discard.
```

Exit zero.

## What this skill does NOT do

- It does not touch the live contextualizer.
- It does not preserve a backup or move the proposed dir to a trash location — `rm -rf` is the operation. If the user wants to keep the `REVIEW.md` audit trail from a discarded proposal, they should copy it out themselves before invoking `discard`.
- It does not unstage upstream-source clones from `~/.cache/skill-engine/`. The cache is independent of the proposed dir; `/skill-engine:clean-cache` is the cache-management surface.
- It does not require sign-off in `REVIEW.md`. Discarding a proposal is the cheapest path out and should not be gated on the user having gone through the predict-then-compare loop.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.