Merge Dependabot PRs
onyx-dot-app/onyx
Triages and lands a batch of open Dependabot PRs in the Onyx repo, where main is gated exclusively by GitHub's merge queue: approves and enqueues green PRs, closes superseded duplicates, fixes…
Guide to software engineering research topics and methodologies
Install Software Engineering Research
$ npx skills add wentorai/research-plugins --skill software-engineering-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wentorai/research-plugins software-engineering-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/domains/cs/software-engineering-research .claude/skills/software-engineering-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "software-engineering-research" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/domains/cs/software-engineering-research into .claude/skills/software-engineering-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wentorai/research-plugins/tree/main/skills/domains/cs/software-engineering-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wentorai/research-plugins --skill software-engineering-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wentorai/research-plugins software-engineering-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/domains/cs/software-engineering-research .agents/skills/software-engineering-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "software-engineering-research" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/domains/cs/software-engineering-research into .agents/skills/software-engineering-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill software-engineering-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wentorai/research-plugins software-engineering-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/domains/cs/software-engineering-research .cursor/skills/software-engineering-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "software-engineering-research" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/domains/cs/software-engineering-research into .cursor/skills/software-engineering-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wentorai/research-plugins.git --path skills/domains/cs/software-engineering-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wentorai/research-plugins --skill software-engineering-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wentorai/research-plugins software-engineering-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/domains/cs/software-engineering-research .gemini/skills/software-engineering-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "software-engineering-research" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/domains/cs/software-engineering-research into .gemini/skills/software-engineering-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wentorai/research-plugins software-engineering-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wentorai/research-plugins --skill software-engineering-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/domains/cs/software-engineering-research .github/skills/software-engineering-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "software-engineering-research" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/domains/cs/software-engineering-research into .github/skills/software-engineering-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill software-engineering-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wentorai/research-plugins software-engineering-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/domains/cs/software-engineering-research .opencode/skills/software-engineering-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "software-engineering-research" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/domains/cs/software-engineering-research into .opencode/skills/software-engineering-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
software-engineering-research- GitHub stars
- 298
- Used in
- 1 other repo
- Token cost
- ~2k tokens
- SKILL.md length
- 433 words
- Files
- 1
- Skills in repo
- 405
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guide to software engineering research topics and methodologies
- Development work in your project
- SKILL.md covers SE Research Subfields, Research Methodologies in SE, Key Datasets and Benchmarks and Static Analysis Tools for…, plus 3 more sections
- Reaches github.com
What it does
Software Engineering Research is an agent skill from wentorai/research-plugins. Guide to software engineering research topics and methodologies
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Python. The repository describes itself as: 350+ academic research skills, MCP configs, and plugins for Research-Claw and AI agents. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/software-engineering-research”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Software Engineering Research loads about 2k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 433 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 433 words, ~2,005 tokens.
Download SKILL.mdSave it as
.claude/skills/software-engineering-research/SKILL.md (or your agent's skills folder).- name
- software-engineering-research
- description
- Guide to software engineering research topics and methodologies
Software Engineering Research Guide
Navigate the landscape of software engineering research, including key subfields, methodologies, datasets, benchmarks, and top venues.
SE Research Subfields
| Subfield | Key Topics | Major Venues |
|---|---|---|
| Software Testing | Test generation, fuzzing, mutation testing, flaky tests | ISSTA, ICST, ASE |
| Program Analysis | Static analysis, abstract interpretation, symbolic execution | PLDI, POPL, OOPSLA |
| Software Maintenance | Code refactoring, technical debt, code smells, evolution | ICSME, MSR, SANER |
| SE for AI/ML | ML pipeline testing, data quality, model debugging | ICSE-SEIP, FSE |
| AI for SE | Code generation, bug detection, program repair | ICSE, FSE, ASE |
| Distributed Systems | Consensus, fault tolerance, scalability, microservices | SOSP, OSDI, EuroSys |
| Cybersecurity | Vulnerability detection, malware analysis, privacy | IEEE S&P, CCS, USENIX Security |
| HCI in SE | Developer tools, IDE usability, code comprehension | CHI, CSCW, VL/HCC |
| Empirical SE | Mining repositories, developer surveys, controlled experiments | ESEM, MSR, TOSEM |
Research Methodologies in SE
Controlled Experiments
Testing a specific hypothesis with treatment and control groups:
Example: Does AI code completion improve developer productivity?
Design:
- Participants: 60 professional developers
- Treatment: IDE with AI code completion enabled
- Control: IDE with AI code completion disabled
- Task: Complete 5 programming tasks of varying difficulty
- Metrics: Task completion time, code correctness, lines of code
- Analysis: Mixed-effects linear model with participant as random effect
Threats to validity:
- Internal: Learning effect (counterbalance task order)
- External: Lab setting may not reflect real development
- Construct: "Productivity" operationalized as speed + correctnessMining Software Repositories (MSR)
Analyzing data from version control, issue trackers, code review systems:
# Example: Analyze commit patterns using PyDriller
from pydriller import Repository
repo_url = "https://github.com/apache/kafka"
commit_data = []
for commit in Repository(repo_url, since=datetime(2023, 1, 1),
to=datetime(2023, 12, 31)).traverse_commits():
commit_data.append({
"hash": commit.hash[:8],
"author": commit.author.name,
"date": commit.committer_date,
"files_changed": commit.files,
"insertions": commit.insertions,
"deletions": commit.deletions,
"message": commit.msg[:100]
})
df = pd.DataFrame(commit_data)
print(f"Total commits in 2023: {len(df)}")
print(f"Unique contributors: {df['author'].nunique()}")
print(f"Avg files per commit: {df['files_changed'].mean():.1f}")Case Studies
In-depth investigation of a phenomenon in its real-world context:
Case Study Protocol (based on Yin, 2018):
1. Research questions: How do teams adopt microservices?
2. Unit of analysis: Development teams at 3 companies
3. Data sources:
- Semi-structured interviews (8-12 per company)
- Architecture documentation review
- Commit history and deployment logs
- Meeting observations
4. Analysis: Thematic analysis with cross-case comparison
5. Validity: Triangulation across data sources, member checkingKey Datasets and Benchmarks
Code Understanding and Generation
| Benchmark | Task | Languages | Size |
|---|---|---|---|
| HumanEval | Code generation from docstrings | Python | 164 problems |
| MBPP | Code generation from descriptions | Python | 974 problems |
| SWE-bench | Real-world GitHub issue resolution | Python | 2,294 instances |
| CodeXGLUE | Multiple code tasks | 6 languages | Varies by task |
| BigCloneBench | Clone detection | Java | 6M clone pairs |
| Defects4J | Bug localization and repair | Java | 835 real bugs |
Software Engineering Process
| Dataset | Content | Use Cases |
|---|---|---|
| GHTorrent | GitHub event data (commits, issues, PRs) | MSR studies |
| Software Heritage | Universal source code archive | Code evolution, provenance |
| Stack Overflow Data Dump | Q&A posts, tags, votes | Developer knowledge, NLP |
| CVE Database | Vulnerability records | Security research |
| Chrome/Firefox Bug Trackers | Bug reports, patches | Bug triage, severity prediction |
Show full SKILL.md (149 more words)Show less
Static Analysis Tools for Research
# Example: Using tree-sitter for AST-level code analysis
from tree_sitter import Language, Parser
import tree_sitter_python as tspython
PYTHON_LANGUAGE = Language(tspython.language())
parser = Parser(PYTHON_LANGUAGE)
source_code = b"""
def fibonacci(n):
if n <= 1:
return n
return fibonacci(n-1) + fibonacci(n-2)
"""
tree = parser.parse(source_code)
root = tree.root_node
def count_nodes(node, node_type):
"""Count AST nodes of a given type."""
count = 1 if node.type == node_type else 0
for child in node.children:
count += count_nodes(child, node_type)
return count
print(f"Function definitions: {count_nodes(root, 'function_definition')}")
print(f"If statements: {count_nodes(root, 'if_statement')}")
print(f"Return statements: {count_nodes(root, 'return_statement')}")
print(f"Function calls: {count_nodes(root, 'call')}")Code Metrics
# Common software metrics
metrics = {
"Lines of Code (LOC)": "Total lines (including blanks and comments)",
"Cyclomatic Complexity": "Number of independent paths (McCabe, 1976)",
"Halstead Volume": "Based on operators and operands count",
"Maintainability Index": "Composite of LOC, CC, and Halstead",
"Coupling Between Objects": "Number of other classes referenced",
"Depth of Inheritance": "Levels in class hierarchy",
"Code Churn": "Lines added + modified + deleted per period",
"Comment Density": "Ratio of comment lines to total lines"
}
# Calculate cyclomatic complexity using radon
# pip install radon
import subprocess
result = subprocess.run(
["radon", "cc", "my_module.py", "-s", "-j"],
capture_output=True, text=True
)
print(result.stdout)Top Venues and Impact
Tier-1 SE Venues
| Venue | Type | Acceptance Rate | Focus |
|---|---|---|---|
| ICSE | Conference | ~22% | Broad SE |
| FSE/ESEC | Conference | ~24% | Broad SE |
| ASE | Conference | ~22% | Automated SE |
| ISSTA | Conference | ~25% | Software testing |
| MSR | Conference | ~30% | Mining repositories |
| TOSEM | Journal | -- | Broad SE (ACM) |
| TSE | Journal | -- | Broad SE (IEEE) |
| EMSE | Journal | -- | Empirical SE (Springer) |
Systems and Security Venues
| Venue | Type | Focus |
|---|---|---|
| SOSP/OSDI | Conference | Operating systems, distributed systems |
| EuroSys | Conference | Systems (Europe) |
| NSDI | Conference | Networked systems design |
| IEEE S&P (Oakland) | Conference | Security and privacy |
| USENIX Security | Conference | Security |
| CCS | Conference | Computer and communications security |
| NDSS | Conference | Network and distributed systems security |
Research Tools Ecosystem
| Tool | Purpose | URL |
|---|---|---|
| PyDriller | Git repository mining (Python) | github.com/ishepard/pydriller |
| Radon | Python code metrics | github.com/rubik/radon |
| SonarQube | Multi-language static analysis | sonarqube.org |
| Understand | Code analysis and metrics | scitools.com |
| Joern | Code analysis platform (CPG) | joern.io |
| CodeQL | Semantic code analysis | codeql.github.com |
| tree-sitter | Incremental parsing library | tree-sitter.github.io |
© wentorai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/domains/cs/software-engineering-research of wentorai/research-plugins.
Open the folder on GitHubat commit bf44b3c
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wentorai/research-plugins, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Software Engineering Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Software Engineering Research this skillwentorai/research-plugins | 298 | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Merge Dependabot PRsonyx-dot-app/onyx | 32k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Code Graph Mermaid Diagramstrailofbits/skills | 7.4k | 1 repos | ~1.7k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Kedro Babysitkedro-org/kedro | 11k | — | ~4k | Automated safety check: Pass | Custom licence | |
| Flowsint Enricher Builderreconurge/flowsint | 9.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Code Review Specialistluongnv89/claude-howto | 42k | — | ~764 | Automated safety check: Pass | MIT |
Similar skills
- Official
Code Graph Mermaid Diagrams
trailofbits/skills
Generates Mermaid diagrams from Trailmark code graphs, including call graphs, class hierarchies, module dependency maps, complexity heatmaps and attack surface data flows.
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
Flowsint Enricher Builder
reconurge/flowsint
Guides building Flowsint enrichers and types: where definitions live, how the base class and vault work, and when a new type is warranted.
Code Review Specialist
luongnv89/claude-howto
Reviews code for security, performance, quality and maintainability, using a checklist, a finding template and two metrics scripts.
- Official
Adk Setup
google/adk-python
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…
More from wentorai/research-plugins
All 405 skills in this repoAbstract Writing Guide
wentorai/research-plugins
Craft structured research abstracts that maximize clarity and journal acceptance
Academic Citation Manager
wentorai/research-plugins
Manage academic citations across BibTeX, APA, MLA, and Chicago formats
Academic Paper Summarizer
wentorai/research-plugins
Summarize academic papers with structured extraction of key elements
Academic Study Methods
wentorai/research-plugins
Evidence-based study techniques for academic learning and retention
Academic Tone Guide
wentorai/research-plugins
Adjust writing tone and register for academic audiences and venues
Academic Translation Guide
wentorai/research-plugins
Academic translation, post-editing, and Chinglish correction guide
Related
Works with
Categories
Questions about Software Engineering Research
What does Software Engineering Research do?
Guide to software engineering research topics and methodologies. Software Engineering Research is an agent skill from wentorai/research-plugins.
When should I use Software Engineering Research?
Software Engineering Research fits situations like: development work in your project.
How do I install Software Engineering Research in Claude Code?
Run `npx skills add wentorai/research-plugins --skill software-engineering-research -a claude-code`. Or copy the skill folder (skills/domains/cs/software-engineering-research in wentorai/research-plugins) into .claude/skills/software-engineering-research in your project. Claude Code loads it when a task matches its description.
How do I install Software Engineering Research in Codex?
Run `npx skills add wentorai/research-plugins --skill software-engineering-research -a codex`. Or copy the skill folder (skills/domains/cs/software-engineering-research in wentorai/research-plugins) into .agents/skills/software-engineering-research in your project. Codex loads it when a task matches its description.
Can I use Software Engineering Research in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wentorai/research-plugins --skill software-engineering-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/software-engineering-research, .gemini/skills/software-engineering-research, .github/skills/software-engineering-research and .opencode/skills/software-engineering-research in your project.
What does Software Engineering Research need to run?
SKILL.md names no scripts, command-line tools or credentials: Software Engineering Research is instructions for the agent only. Our summary lists: Python 3.
Does Software Engineering Research access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Software Engineering Research safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Software Engineering Research use?
Software Engineering Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Software Engineering Research use?
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Software Engineering Research?
Skills that share tags, products or a category with Software Engineering Research: Merge Dependabot PRs (onyx-dot-app/onyx, 32k stars), Code Graph Mermaid Diagrams (trailofbits/skills, 7.4k stars), Kedro Babysit (kedro-org/kedro, 11k stars) and Flowsint Enricher Builder (reconurge/flowsint, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Software Engineering Research?
wentorai (a GitHub user) maintains it in wentorai/research-plugins, which has 298 GitHub stars. The repository holds 405 skills in this directory. The repository was last updated on June 19, 2026.
Source: wentorai/research-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.