awesome-copilot/.github/workflows/resource-staleness-report.md

description, on, permissions, tools, safe-outputs

description	on	permissions	tools	safe-outputs
Weekly report identifying stale and aging resources across agents, prompts, instructions, hooks, and skills folders	schedule weekly	contents read	github toolsets repos	create-issue noop max close-older-issues 1 true

Resource Staleness Report

You are an AI agent that audits the resources in this repository to identify ones that may need attention based on how long it has been since their last meaningful change.

Your Task

Analyze all files in the following directories to determine when each file last had a major (substantive) change committed:

• agents/ (.agent.md files)
• prompts/ (.prompt.md files)
• instructions/ (.instructions.md files)
• hooks/ (folders — check the folder's files)
• skills/ (folders — check the folder's files)

What Counts as a Major Change

A major change is one that modifies the actual content or behavior of the resource. Use git log with --diff-filter=M and --follow to find when files were last substantively modified.

Ignore the following — these are NOT major changes:

• File renames or moves (R status in git)
• Whitespace-only or line-ending fixes
• Commits whose messages indicate bulk formatting, renaming, or automated updates (e.g., "fix line endings", "rename files", "bulk update", "normalize")
• Changes that only touch frontmatter metadata without changing the instructions/content body

How to Determine Last Major Change

For each resource file, run:

git log -1 --format="%H %ai" --diff-filter=M -- <filepath>

This gives the most recent commit that modified (not just renamed) the file. If a file has never been modified (only added), use the commit that added it:

git log -1 --format="%H %ai" --diff-filter=A -- <filepath>

For hook and skill folders, check all files within the folder and use the most recent major change date across any file in that folder.

Classification

Based on today's date, classify each resource:

• 🔴 Stale — last major change was more than 30 days ago
• 🟡 Aging — last major change was between 14 and 30 days ago
• Resources changed within the last 14 days are fresh and should NOT be listed

Deeper Review for the Oldest Stale Resources

After producing the age-based inventory, perform a content review of the 10 oldest stale resources.

For each of those 10 resources:

1. Read the current file contents (for hooks and skills, inspect the folder's primary instruction file and any bundled files that materially affect behavior).
2. Determine whether the resource is:
   • Materially stale — guidance is outdated, incomplete in an important way, or references older patterns that should be replaced
   • Problematic — guidance is misleading, harmful, overly broad, or likely to produce poor results even if it is not version-stale
   • Mostly current — old by date, but still broadly aligned with current best practices
3. Identify the most important concrete issues. Focus on substantive problems, not minor wording nits.
4. Recommend what should be done next:
   • Immediate rework/removal
   • Targeted refresh
   • Minor modernization
   • No urgent change needed

Do not assume that old automatically means bad. The deeper review should separate truly risky resources from ones that are simply old.

Output Format

Create an issue with the title: 📋 Resource Staleness Report

Organize the issue body as follows:

### Summary

- **Stale (>30 days):** X resources
- **Aging (14–30 days):** Y resources
- **Fresh (<14 days):** Z resources (not listed below)

### 🔴 Stale Resources (>30 days since last major change)

| Resource | Type | Last Major Change | Days Ago |
|----------|------|-------------------|----------|
| `agents/example.agent.md` | Agent | 2025-01-15 | 45 |

### 🟡 Aging Resources (14–30 days since last major change)

| Resource | Type | Last Major Change | Days Ago |
|----------|------|-------------------|----------|
| `prompts/example.prompt.md` | Prompt | 2025-02-01 | 20 |

### Deep Review: 10 Oldest Stale Resources

| Resource | Verdict | Key Problems | Recommended Action |
|----------|---------|--------------|--------------------|
| `instructions/example.instructions.md` | Materially stale | References older framework defaults and misses current patterns | Targeted refresh |

### Priority Actions

1. Immediate rework/removal: `resource-a`, `resource-b`
2. Targeted refresh: `resource-c`, `resource-d`
3. Minor modernization: `resource-e`
4. No urgent change needed: `resource-f`

If a category has no resources, include the header with a note: "✅ No resources in this category."

Use <details> blocks to collapse sections with more than 15 entries.

Guidelines

• Process all resource types: agents, prompts, instructions, hooks, and skills.
• For hooks and skills, treat the entire folder as one resource. Report it by folder name and use the most recent change date of any file within.
• Sort tables by "Days Ago" descending (oldest first).
• After building the stale table, inspect the 10 oldest stale resources in more depth and include the deeper review section.
• In the deeper review, prefer high-signal issues: outdated version assumptions, deprecated APIs, misleading instructions, harmful heuristics, unsafe defaults, or instructions that are scoped too broadly.
• If a resource is old but still sound, explicitly say so. The goal is to prioritize maintenance work, not just restate age.
• Keep the deeper review concise but specific. Each row should explain the main problem and the best next step.
• If there are no stale or aging resources at all, call the noop safe output with the message: "All resources have been updated within the last 14 days. No staleness report needed."
• Do not include fresh resources in the tables — only mention the count in the summary.
• Use the create-issue safe output to file the report. Previous reports will be automatically closed.