manastalukdar/ai-devstudio

contributing

Contribution readiness assessment analyzing project guidelines and requirements

First seen Feb 21, 2026

Installation

$ npx skills add manastalukdar/ai-devstudio --skill contributing

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 manastalukdar/ai-devstudio · top by installs.

npx skills add manastalukdar/ai-devstudio

Browse all from manastalukdar/ai-devstudio

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 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 1
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,605 B
  • docs SUMMARY.md 99 B

History

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

SKILL.md

Complete Contribution Strategy - Context Aware

I'll analyze everything needed for your successful contribution based on your current context and work.

Strategic Thinking Process

<think> For a successful contribution, I need to analyze:

  1. Current Work Context

- What has been done in this session? - Are we mid-implementation or post-completion? - What type of changes were made (feature, fix, refactor)? - Is the work ready for contribution?

  1. Project Type & Standards

- Is this open source, company, or personal project? - What are the contribution guidelines? - Are there specific workflows to follow? - What quality gates exist (tests, lint, reviews)?

  1. Contribution Strategy

- Should this be one PR or multiple? - Which issues does this work address? - What documentation needs updating? - Who should review this?

  1. Pre-flight Checklist

- Do all tests pass? - Is the code properly formatted? - Are there any lint warnings? - Is documentation updated? - Are commits well-organized? </think>

Token Optimization

Expected range: 500–1,500 tokens (initial), 100 tokens (cache hit)

Caching: Caches project structure in .claude/cache/understand/project_structure.json for 7 days.

Early exit: Returns immediately if CONTRIBUTING.md already exists and is current.

Patterns used: Grep-before-Read, early exit, template-based generation, caching