agentleFS
Sign inStart free
hugobatistahugobatista/agent-skills/skills/devops/github-templates/SKILL.md

github-templates

Skill1 starsChanged 53 days agoMITView on GitHub

Create GitHub issue and pull request templates for GitHub-hosted projects. Covers bug reports, feature requests, PR templates, and contributing guidelines. Proactively offers during project initialization.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create GitHub community files (issue templates, PR template, contributing guide) for any GitHub-hosted project.

    line 9
  2. Distinctive:

    Ask the user: *"Will this project be hosted on GitHub?"*

    line 15
  3. Distinctive:

    Check which of these already exist:

    line 22
  4. Distinctive:

    Read the project's configuration files to detect:

    line 34
  5. Distinctive:

    Ask the user which templates to create.

    line 79
  6. Distinctive:

    If the user declines all, exit.

    line 92
  7. Distinctive:

    Ask the user for:

    line 96
  8. Very specific:

    Read each selected .tmpl file, substitute placeholders, and write:

    line 103
  9. Distinctive:

    Create directories as needed:

    line 114
  10. Very specific:

    Write each template file. For CONTRIBUTING.md, use the assets/CONTRIBUTING.md.tmpl template.

    line 119
  11. Distinctive:

    After writing, list the created files for the user.

    line 123

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

github-templates

Create GitHub community files (issue templates, PR template, contributing guide) for any GitHub-hosted project.

Workflow

Step 1: Check if project will be on GitHub

Ask the user: "Will this project be hosted on GitHub?"

  • If yes: proceed
  • If no: explain that this skill is for GitHub projects only, and skip

Step 2: Scan existing templates

Check which of these already exist:

  • .github/ISSUE_TEMPLATE/bug_report.md
  • .github/ISSUE_TEMPLATE/feature_request.md
  • .github/ISSUE_TEMPLATE/config.yml
  • .github/PULL_REQUEST_TEMPLATE.md
  • CONTRIBUTING.md

List which ones exist and which are missing.

Step 3: Gather project metadata

Read the project's configuration files to detect:

InfoSource
Project namepyproject.toml → [project].name or package.json → name or directory name
Language/runtimePython (pyproject.toml), Node (package.json), Go (go.mod), Rust (Cargo.toml)
Validation commandPython/uv → uv run hatch run check if hatch scripts present, else uv run pytest && uv run ruff check . && uv run mypy; Node → npm test && npm run lint if scripts present; otherwise fallback to generic
Docs URLCheck README.md for a docs link; otherwise pyproject.toml for Project-URL
Python versionpyproject.toml → requires-python
Package manageruv.lock → uv, package-lock.json → npm, pnpm-lock.yaml → pnpm

For the prerequisites and setup steps in assets/CONTRIBUTING.md.tmpl:

Python projects (pyproject.toml found):

prerequisites: >
  - **Python {{python_version}}**  
  - **uv** (installed globally) — see [docs.astral.sh/uv](https://docs.astral.sh/uv/)
setup_steps: >
  4. Install dependencies:
     ```bash
     uv sync --group dev
     ```

Node projects (package.json found):

prerequisites: >
  - **Node.js {{node_version}}**  
  - **npm** (or **pnpm** / **yarn** depending on lock file)
setup_steps: >
  4. Install dependencies:
     ```bash
     npm install
     ```

Other projects:

prerequisites: "" (omit section)
setup_steps: "" (omit section)

Step 4: Present options

Ask the user which templates to create. Pre-check all missing items by default.

The following files are missing:
☑ .github/ISSUE_TEMPLATE/bug_report.md
☑ .github/ISSUE_TEMPLATE/feature_request.md  
☑ .github/ISSUE_TEMPLATE/config.yml
☑ .github/PULL_REQUEST_TEMPLATE.md
☑ CONTRIBUTING.md

Create all of these?

If the user declines all, exit.

Step 5: Ask for customization values

Ask the user for:

  • Docs URL (optional) — if not found in project config, prompt: "Do you have a documentation URL? (leave blank to skip)"
  • Validation command — offer the detected value as default, let user override
  • Author/maintainer name — for CONTRIBUTING.md tone (default: detected from git config user.name)

Step 6: Substitute and write templates

Read each selected .tmpl file, substitute placeholders, and write:

PlaceholderSource
{{project_name}}Project name from config (Step 3)
{{docs_url}}User-provided or empty (if provided, the conditional {{#if docs_url}} blocks render)
{{validation_command}}Detected or user-overridden
{{prerequisites}}Generated from project type
{{setup_steps}}Generated from project type
{{python_version}}From requires-python in pyproject.toml

Create directories as needed:

mkdir -p .github/ISSUE_TEMPLATE

Write each template file. For CONTRIBUTING.md, use the assets/CONTRIBUTING.md.tmpl template.

Step 7: Confirm

After writing, list the created files for the user.

Created:
  .github/ISSUE_TEMPLATE/bug_report.md
  .github/ISSUE_TEMPLATE/feature_request.md
  .github/ISSUE_TEMPLATE/config.yml
  .github/PULL_REQUEST_TEMPLATE.md
  CONTRIBUTING.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free