contentstack/datasync-asset-store-filesystem · Archived

code-review

PR review checklist for datasync-asset-store-filesystem — use when opening or reviewing pull requests.

First seen Jun 17, 2026

Installation

$ npx skills add contentstack/datasync-asset-store-filesystem --skill code-review

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from contentstack/datasync-asset-store-filesystem.

npx skills add contentstack/datasync-asset-store-filesystem

Browse all from contentstack/datasync-asset-store-filesystem

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch master
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,125 B
  • docs SUMMARY.md 123 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Code review – DataSync Asset Store Filesystem

When to use

  • Opening a PR that touches src/, tests, or published artifacts
  • Reviewing changes for a library release

Instructions

  • Build and tests: Branch should pass npm run build-ts and npm test locally.
  • Lint: Run npm run tslint for TypeScript changes in src/.
  • API and docs: If public behavior or defaults change, update root README.md and verify [datasync-asset-store](../datasync-asset-store/SKILL.md) assumptions still hold.
  • Versioning: Bump package.json version when releasing; follow org conventions for tags and changelog if applicable.
  • Security: Avoid logging secrets; path handling should remain safe (see existing sanitization in src/utils.ts and related code). Large dependency or HTTP behavior changes deserve extra scrutiny.
  • Scope: Keep changes focused on the asset-store concern—avoid unrelated refactors in the same PR unless required for the fix.