project-archive-done

Original：🇨🇳 Chinese

Translated

Batch archive project items with Status set to Done using `gh project item-archive`. Also checks and guides on the configuration status of the Auto-archive built-in workflow (manual execution is basically unnecessary if enabled). Used for scenarios like "archive completed items", "organize Done items", "clean up the board", etc.

2installs

Sourcefandhe-ai/agent-cli-skills

Added on2026-05-11

NPX Install

npx skill4agent add fandhe-ai/agent-cli-skills project-archive-done

SKILL.md Content (Chinese)

View Translation Comparison →

project-archive-done

Archive completed (Done) items in the project to organize the board. Also checks the status if the built-in Auto-archive is configured.

Prerequisites

Completed items exist in the target GitHub Project
The
```
gh
```
CLI is installed and authenticated (with the
```
project
```
scope)

Flow

Step 1: Check Auto-archive status

If the built-in Auto-archive workflow is enabled, items will be archived automatically. Confirm the configuration status with the user.

Configuration URL:

https://github.com/orgs/<owner>/projects/<number>/workflows

(For personal projects:

https://github.com/users/<owner>/projects/<number>/workflows

)

Auto-archive enabled → Execution of this skill is basically unnecessary. Continue only if you want to archive immediately
Auto-archive disabled → Perform manual archiving with this skill. Guide users to enable Auto-archive if needed

Step 2: Retrieve project items

bash

gh project item-list <number> \
  --owner <owner> \
  --format json \
  --limit 999

Step 3: Retrieve field metadata

bash

gh project field-list <number> \
  --owner <owner> \
  --format json

Identify the ID of the Status field and the ID of the "Done" option.

Step 4: Filter completed items

Extract items with Status set to "Done" from the results of Step 2.

If

--query

is available:

bash

gh project item-list <number> \
  --owner <owner> \
  --query "status:Done" \
  --format json

Step 5: Confirm with the user

Display items to be archived:

The following N completed items will be archived:
- #42: feat: Social Login (Done)
- #43: fix: Validation Error (Done)
- #44: docs: API Documentation Update (Done)

Do you want to proceed?

Step 6: Execute archiving

Archive each item:

bash

gh project item-archive <number> \
  --owner <owner> \
  --id <item-id>

Step 7: Report results

## Archiving Results

- Archived: N items
- Remaining active items: M items
- Completed items on board: 0 items

If Auto-archive is disabled, recommend enabling it:

💡 Enabling Auto-archive will automatically archive items N days after they are marked Done.
Configuration: <workflows URL>

Notes

Always obtain user confirmation before archiving
Archiving can be undone (
```
gh project item-archive --undo
```
)
Archived items are hidden from the project view but not deleted
Using together with the Auto-archive built-in workflow reduces the frequency of manual execution
It is also possible to filter and archive items based on specific conditions (date range, labels, etc.)
Using
GIT_SSL_NO_VERIFY=1
in sandbox environments: Refer to the "Execution in sandbox environments" section below for details

Execution in sandbox environments

When running this skill in a sandbox environment, consider using

GIT_SSL_NO_VERIFY=1

for GitHub operations over the network. The main remote operation of this skill is

gh project item-archive

, and the "remote write" determination is Required (this skill mainly uses APIs). For details on command classification and precautions for disabling TLS verification, refer to

docs/sandbox-tls.md

.

project-archive-done

NPX Install

Tags

SKILL.md Content (Chinese)

project-archive-done

Prerequisites

Flow

Step 1: Check Auto-archive status

Step 2: Retrieve project items

Step 3: Retrieve field metadata

Step 4: Filter completed items

Step 5: Confirm with the user

Step 6: Execute archiving

Step 7: Report results

Notes

Execution in sandbox environments