AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL unreviewed MIT Self-run

Repository Maintenance

skill-mishrashardendu22-agent-skills-repository-maintenance · by MishraShardendu22

>-

— No reviews yet
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-mishrashardendu22-agent-skills-repository-maintenance

Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.

Security review

⚠ Flagged

1 finding(s); flagged for manual review. · v0.1.0 How review works →

  • • Prompt-injection patterns
  • • Secret / credential exfiltration
  • • Dangerous shell & filesystem operations
  • • Untrusted network calls
  • • Known-malicious package signatures
  • high Destructive filesystem operation.

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Reliability & compatibility

— Not yet reviewed
0 installs to date
— no reviews yet
● 25d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Repository Maintenance? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Repository Maintenance Skill

This skill provides procedures for maintaining database integrity, executing database backups, applying schema migrations, and managing dependencies across the GitHub Backup Automation System.

1. Branch-First Development

> [!IMPORTANT] > CREATE A LOCAL BRANCH FIRST: Always start by creating a local branch from main: > ``bash > git switch -c MishraShardendu22/main/ > ` > Never apply maintenance or schema changes directly on main`.


2. Database Schema Integrity & Migrations

> [!CAUTION] > CRITICAL RULE: Never execute destructive SQL statements (DROP TABLE, TRUNCATE). Production data has historical backup logs spanning months.

Migration Rules

  • All migrations MUST be located in backend/db/migrations/ using versioned naming NNNNNN_.up.sql and NNNNNN_.down.sql.
  • All SQL statements MUST be idempotent:
  • CREATE TABLE IF NOT EXISTS ...
  • CREATE INDEX IF NOT EXISTS ...
  • ALTER TABLE ... ADD COLUMN IF NOT EXISTS ...
  • Schema migrations are orchestrated exclusively by Go backend startup (backend/db/migrator.go).

2. Backup & Disaster Recovery Runbook

PostgreSQL database dumps are automated with SHA-256 integrity verification:

# 1. Execute an automated database backup (stored in backups/postgres/ with 14-day retention)
make backup-db

# 2. Restore database from a backup file
make restore-db BACKUP_FILE=backups/postgres/gbm_pg_backup_YYYYMMDD_HHMMSS.sql.gz

3. Dependency Management

  • Go Dependencies: Managed via go.mod. Update with go get -u and clean with go mod tidy.
  • Python Observatory: Managed via uv in agentic-observatory/. Update with uv lock --upgrade and sync with uv sync.
  • Frontend Dashboard: Managed via pnpm in frontend/. Update with pnpm update. Ensure native modules like sharp and @biomejs/biome remain authorized in frontend/pnpm-workspace.yaml.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.