developer-setup

Automate one-time developer workflow onboarding across multiple GitHub repositories.

12.6k|1.5k|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/nearai/ironclaw --skill developer-setup-nearai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-setup
Source: https://github.com/nearai/ironclaw/tree/main/skills/developer-setup
Command: npx skills add https://github.com/nearai/ironclaw --skill developer-setup-nearai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly establish a complete, secure developer workflow for multiple GitHub repos so you can track commitments, automate PR/CI triage, and run repeatable reviews without manual setup every time.

Core Features & Use Cases

  • One-time onboarding for developer workflow: installs GitHub workflow missions, registers projects per repo, and initializes the commitments workspace.
  • Creates a commitments workspace: sets up the required folder structure for open/resolved signals, decisions, parked ideas, and tech debt.
  • Configures recurring developer missions: generates scheduled missions for triage, morning digests, stale PR checks, weekly retro, tech-debt resurfacing, and decision-outcome follow-ups.

Quick Start

Ask your assistant: "Run developer-setup for my GitHub workflow, set up my commitments workspace, and create the PR/CI triage and weekly retro missions for my repos."

Frequently Asked Questions about developer-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an automated GitHub developer workflow across multiple repositories?

Automated GitHub developer workflow setup configures multi-repo onboarding by initializing commitments workspaces, registering per-repo projects, and installing workflow missions for PR review management and CI failure triage.

How do I track technical debt extracted from GitHub pull request review comments?

Tracking technical debt from PR reviews is handled by configuring recurring developer missions that extract commitments from review comments and store them within a dedicated commitments workspace folder structure.

What's the best way to automate recurring GitHub PR triage and stale pull request checks?

Automating recurring GitHub PR triage and stale pull request checks requires configuring scheduled mission cadences with GitHub API validation, generating morning digests, and running weekly retrospectives.

Does this developer workflow setup require manual configuration for each individual GitHub repository?

No, the developer workflow setup performs one-time onboarding across multiple GitHub repositories, applying safety-minded guardrails and setup-marker gating to avoid manual configuration for each individual project.

Can I automate decision logging and follow-up tracking for my GitHub development cycle?

Yes, automating decision logging and follow-up tracking is supported by creating a commitments workspace that logs decisions and schedules recurring missions for decision-outcome follow-ups.

What limitations or guardrails apply when configuring scheduled GitHub workflow missions?

Scheduled GitHub workflow missions operate under safety-minded guardrails with GitHub API validation, requiring setup-marker gating to be satisfied before configuring recurring triage, digest, and retrospective cadences.