Habilidades git-pr-workflows-onboard
📦

git-pr-workflows-onboard

Seguro

Create personalized onboarding plans for new hires

New employee onboarding often lacks structure and consistency, leading to slow ramp-up and poor retention. This skill transforms onboarding into a systematic process with role-specific plans, measurable milestones, and proven integration strategies.

Suporta: Claude Codex Code(CC)
🥉 74 Bronze
1

Baixar o ZIP da skill

2

Upload no Claude

Vá em Configurações → Capacidades → Skills → Upload skill

3

Ative e comece a usar

Testar

A utilizar "git-pr-workflows-onboard". Create Day 1 checklist for new remote software engineer

Resultado esperado:

  • Morning: Manager welcome (30 min), HR paperwork (45 min), company culture overview (30 min), team standup observation (15 min)
  • Afternoon: Virtual lunch with buddy (60 min), laptop setup with IT (90 min), Slack and tools configuration (30 min), first Git commit ceremony (30 min)
  • End of day: Feedback survey (10 min), preparation for Day 2 agenda review

A utilizar "git-pr-workflows-onboard". What should a 30-day milestone include for a backend engineer

Resultado esperado:

  • Complete all mandatory training modules and security certifications
  • Merge at least 3 pull requests including one bug fix deployed to production
  • Document one unclear process or system for future onboarding
  • Present key learnings to team in 10-minute lightning talk
  • Receive and discuss manager feedback with adjustment plan

Auditoria de Segurança

Seguro
v1 • 2/25/2026

All 21 static analysis findings are false positives. The 'external_commands' detections reference markdown documentation and checklist examples, not actual shell execution. The 'cryptographic' and 'reconnaissance' patterns matched innocent text in onboarding documentation. This skill generates text-based onboarding plans with no code execution capabilities.

1
Arquivos analisados
419
Linhas analisadas
0
achados
1
Total de auditorias
Nenhum problema de segurança encontrado
Auditado por: claude

Pontuação de qualidade

38
Arquitetura
100
Manutenibilidade
87
Conteúdo
50
Comunidade
100
Segurança
91
Conformidade com especificações

O Que Você Pode Construir

Software Engineer Onboarding

Create comprehensive 30/60/90 day plan for new developer including development environment setup, first PR guidance, codebase immersion activities, and team integration milestones.

Remote Employee Integration

Generate remote-specific onboarding plan with virtual orientation sessions, async communication norms, timezone-friendly scheduling, and home office setup guidance.

Senior Hire Accelerated Onboarding

Build fast-track onboarding for senior or lead hires including leadership introductions, architecture deep-dives, stakeholder mapping, and early ownership opportunities.

Tente Estes Prompts

Basic Onboarding Plan 
Create an onboarding plan for a new Software Engineer starting next Monday. Role: mid-level backend developer. Team: 8 person platform team. Location: remote in EST timezone. Tech stack: Python, PostgreSQL, AWS.
Comprehensive Onboarding with All Phases 
Generate a complete onboarding plan including pre-arrival preparation, Day 1 agenda, Week 1 technical immersion, and 30/60/90 day milestones. New hire: Senior Frontend Engineer joining a hybrid team. Include React/TypeScript setup, team integration activities, and measurable success criteria for each milestone.
Remote-Specific Onboarding 
Create an onboarding plan optimized for a fully remote new hire across 4 timezones. Include: virtual orientation schedule, async communication guidelines, home office setup checklist, virtual team bonding activities, and strategies to prevent isolation. Role: Product Designer.
Leadership Onboarding Plan 
Build an accelerated onboarding plan for a new Engineering Manager. Include: leadership team introductions, 1:1 schedule with direct reports, current project briefings, team health assessment framework, and first 90 day leadership goals. Team size: 12 engineers across 3 squads.

Melhores Práticas

  • Customize onboarding plans based on role, seniority, and team context rather than using generic templates
  • Assign a dedicated onboarding buddy for the first 30 days with structured responsibilities and daily check-ins
  • Document everything during onboarding to create reusable artifacts for future new hires
  • Track measurable metrics like time to first commit and time to first production deploy
  • Prioritize human connection and team integration alongside technical setup and training

Evitar

  • Using one-size-fits-all onboarding without accounting for role differences or experience levels
  • Overwhelming new hires with too much information in the first week without prioritization
  • Focusing only on technical setup while neglecting team culture and relationship building
  • Leaving new hires without structured support or clear expectations after Day 1 orientation

Perguntas Frequentes

How long should a complete onboarding process take?
Effective onboarding spans 90 days with structured milestones at 30, 60, and 90 days. Day 1 focuses on welcome and setup, Week 1 on immersion, and the full 90 days enables progression from observation to independent contribution.
What makes remote onboarding different from in-person onboarding?
Remote onboarding requires intentional virtual connection activities, async communication training, timezone-aware scheduling, and explicit documentation of norms that in-person teams absorb organically through physical presence.
How do I measure onboarding success?
Track metrics like time to first commit, time to first production deploy, completion of training milestones, knowledge retention assessments, and new hire satisfaction scores through weekly pulse surveys.
What is the buddy system and why is it important?
The buddy system pairs a new hire with an experienced team member for 30 days. Buddies provide daily check-ins, answer questions, guide through processes, and serve as a safe channel for concerns. This accelerates integration and reduces new hire anxiety.
How should onboarding differ for senior or lead hires?
Senior hires need accelerated technical immersion, leadership introductions, early ownership opportunities, and involvement in architectural decisions. Compress the timeline while adding stakeholder mapping and strategic context sessions.
What if a new hire is struggling during onboarding?
Increase buddy check-in frequency, schedule additional manager 1:1s, identify specific knowledge gaps, adjust the plan pace, and consider pairing with different team members. Early intervention in the first 30 days prevents longer-term issues.

Detalhes do Desenvolvedor

Autor

sickn33

Licença

MIT

Repositório

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/git-pr-workflows-onboard

Referência

main

Estrutura de arquivos

📄 SKILL.md