JSdotNet
Community@JSdotNet
JSdotNet publishes devbook specification-driven development skills for .NET repositories, covering chapter review, drift verification, scheduled maintenance, and pull request lifecycle management.
Agent Skills by JSdotNet
Showing 38 vetted skills indexed across 1 GitHub repositories.
JSdotNetchapter-review
Reviews a devbook chapter and records findings as annotation fences with a verdict in its meta block.
JSdotNetchapter-approve
Records human approval decisions on devbook domain chapters with metadata and annotation handling.
JSdotNetchapter-accept
Records human acceptance decisions on approved devbook domain chapters with evidence review.
JSdotNetchapter-handoff
Records a review request on a devbook chapter and builds the reviewer's brief.
JSdotNetchapter-review-queue
Sweeps devbook folders for pending reviews, approvals, and unresolved notes grouped by owner.
JSdotNetinit
Installs repository-owned procedure skills with per-host wrappers and stamps them in config.json.
JSdotNetupdate
Reconciles adopted procedure skills with the installed devbook-procedures release after upgrades.
JSdotNetschedule-review
Runs a layered automated code review combining TODO collection, improvement suggestions, and structured checklist analysis.
JSdotNetschedule-package-update
Updates outdated NuGet packages in .NET solutions and opens a pull request with verified changes.
JSdotNetschedule-devbook-verify
Runs unattended drift checks comparing devbook chapters against code and opens GitHub issues for divergences.
JSdotNetschedule-morning-brief
Generates a one-screen daily brief of repository changes and items needing attention.
JSdotNetschedule-merge-review
Reviews open GitHub pull requests and posts one findings comment with a merge verdict per head commit.
JSdotNetschedule-instruction-review
Tightens repository instruction files and lands cuts as a draft pull request.
JSdotNetschedule-weekly-update
Generates a weekly repository update summarizing shipped work, open items, issues, releases, and failed runs.
JSdotNetschedule-issue-sweep
Triage open GitHub issues, close resolved ones, and resolve the rest as draft pull requests.
JSdotNetschedule-tech-update
Refreshes technology-graph chapters from package inventories and opens a draft pull request.
JSdotNetschedule-week-starter
Fetches release notes and announcements from configured sources to generate a weekly digest.
JSdotNetschedule-performance-review
Scans a codebase for performance issues, scores findings, and implements the top fix via pull request.
JSdotNetschedule-weekly-cost-analysis
Analyzes recorded token usage from weekly flow runs and produces prioritized cost-reduction recommendations.
JSdotNetschedule-status
Reports repository schedules, recent run outcomes, and published artifacts from the host scheduler.
JSdotNetschedule-run
Fires a repository schedule on demand and reports the resulting run.
JSdotNetannotation-sweep
Deletes resolved annotation fences from devbook chapters before branch merges.
JSdotNetvalidate
Validate devbook Markdown chapters against the schema and repair reported metadata errors.
JSdotNetcapture-specs
Plan devbook chapter updates by comparing implementations and tests against existing specifications.
Frequently Asked Questions About JSdotNet
FAQPage SchemaWhat tasks can I accomplish using JSdotNet's skills?▼
You can review, approve, and accept devbook specification chapters; detect drift between chapters and code; capture specs from implementations; run scheduled security, performance, and dependency reviews; sweep and triage issues; and drive pull requests to merge-ready state with branch updates and CI check fixes.
Who are JSdotNet's skills designed for?▼
They target .NET developers and repository maintainers practicing specification-driven development, plus leads running approval gates on chapters and delivered work. SRE-adjacent users benefit from Azure Monitor alert triage into GitHub issues, Jira tickets, or Markdown chapters.
How do I install and run these skills in a repository?▼
Run the init skill to seed start, show, capture, and debug procedure skills under .agents/skills/ with managed wrappers, stamped in .devbook/config.json. Use update after upgrades, doctor to diagnose installation drift, and schedule-run to fire any configured schedule outside its cadence.
What are the prerequisites and dependencies for these skills?▼
Skills assume a GitHub-hosted repository, typically a .NET solution using NuGet with Central Package Management and optionally Aspire AppHost. Devbook skills require adopted .devbook folders; scheduled skills rely on repository-configured cadences; some integrate Jira, Azure Monitor, or Playwright for validation depth.
Do the scheduled skills merge or approve changes automatically?▼
No. Scheduled skills like merge-review, tech-update, and devbook-validate land results as draft pull requests or issues and never approve, merge, or push. Approval and acceptance decisions remain explicit human gates recorded on the devbook chapter with approver and timestamp.